Bug 1513502 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Ah, this issue continues to be kind of mind-bending!

Re: your STR: 
- When I navigate to header-nav inside Markup, I always see Container pane first. This seems correct to me.
- If I navigate to it via picker or context menu, I see Item first. This seems wrong to me.

This is my reasoning from before:

>1. When selecting an Item-Container via Markup view: I think we should change the current behavior to show the Container pane first. It's the most relevant to the page overlay, which seems like the most helpful initial thing to know about a flex-related layout. The higher level overview of the container pane also seems like a more easily understandable first impression for users who aren't necessarily aware of Flex features yet.
>
>2. When navigating to an Item-Container from within the Layout panel: We'd show the Item pane first, as we do now.

So my main reason to show container first when navigating from outside the Layout panel is to anchor on what the page overlay highlights. I think this will make sense once we have the combined overlay/box model highlighter. Happy to chat more if this seems wrong to you.
Ah, this issue continues to be kind of mind-bending!

Re: your STR: 
- When I navigate to header-nav inside Markup, I always see Container pane first. This seems correct to me.
- If I navigate to it via picker or context menu, I see Item first. This seems wrong to me.

This is my reasoning from before:

>1. When selecting an Item-Container via Markup view: I think we should change the current behavior to show the Container pane first. It's the most relevant to the page overlay, which seems like the most helpful initial thing to know about a flex-related layout. The higher level overview of the container pane also seems like a more easily understandable first impression for users who aren't necessarily aware of Flex features yet.
>
>2. When navigating to an Item-Container from within the Layout panel: We'd show the Item pane first, as we do now.

So my main reason to show container first when navigating from outside the Layout panel is to anchor on what the page overlay highlights. I think this will make more sense once we have the combined overlay/box model highlighter. Happy to chat more if this seems wrong to you.

Back to Bug 1513502 Comment 5