Toolbar Roles behavior

I have tried a lot of codes to see what’s the difference between browser and editor, but I can’t find some changes between those two things, so i’m wondering what’s the difference between browser and editor?

Answered by DTS Engineer in 716785022

The browser toolbar role is typically for units of content that you navigate to over time, similar to a browser visiting web pages. The document role is typically for content you treat as a single unit, such as a document stored in a file. They look similar, but the default menu on the title contains items for navigation (browser) or items for manipulating storage (document).

If your app doesn't exactly fit into one of the 3 roles, that's OK. You can start with a role that's most similar to the functionality you want, then customize the toolbar from there.

Accepted Answer

The browser toolbar role is typically for units of content that you navigate to over time, similar to a browser visiting web pages. The document role is typically for content you treat as a single unit, such as a document stored in a file. They look similar, but the default menu on the title contains items for navigation (browser) or items for manipulating storage (document).

If your app doesn't exactly fit into one of the 3 roles, that's OK. You can start with a role that's most similar to the functionality you want, then customize the toolbar from there.

I have find some changes when pushing a navigationLink.

In I understanding, browsing role let you know the page you came from, so you will get a great experience across different pages just like a browser.

The Editor rule let you focus on a single view so that it will not show you where you came from when you're in a new view. It would just show a "back"(<) symbol.

Toolbar Roles behavior
 
 
Q