Hello,
I’m trying to understand why the data-save-bar exists, it seems like the ui-save-bar is better in every possible use case. Unless I’m missing something, I feel like it would be better to just get rid of it or make a big banner on the top of the page in the docs that says like “data-save-bar is for *this specific use case*, ui-save-bar should be used most of the time.
The reason I mention this is because I didn’t realize ui-save-bar existed for a while so I spent so many hours fighting with form states and input types to get the data-save-bar to work. When I switched to ui-save-bar, it was so much easier to set up.
I get if there are certain cases where data-save-bar is better, I just wish the docs made it more clear because right now the language on the pages is quite confusing. Especially on the data-save-bar page where it says “It can be controlled declaratively through the ui-save-bar element. For more information, refer to the ui-save-bar component.” It makes it seem like you must have data-save-bar on the page but you can control it with ui-save-bar. I think it would be more accurate to call the existing Save Bar page “Data Save Bar” or make it clearer somehow.
Sorry if I’m being lecture-y, I just don’t want others to make that same mistake because it cost me sooo much time.
Thanks for reading and have a great day!