@jbinda Just curious how is it acting when we have paragraph & heading blocks down in the hierarchy and directly tap on them?

@iamthomasbishop this needs a design review, could you be able to take a look at the screen capture here WordPress/gutenberg#17547

It’s really great to see the hierarchy navigation in practice, great work so far. I have a few requests, some of which are relevant to other in-progress PRs.

• Padding’s/margins jumping around a bit make navigating the hierarchy a bit clunky/jumpy. More on that here
• The dotted border style (on child blocks) is a bit stronger than the proposed style. Let’s dim the color to match the prototype
• Another thing I’ve already mentioned but worth noting again – it would be beneficial to show the icon of the selected block on the quick toolbar. This would add clarity to what is selected.

I’ll take another look tomorrow, but these are the things that jumped out at me first.

@pinarol paragraph and heading block gets immediately selected after click whatever level it's is.

I know why but didn't figured out the solution yet. I described it more here (#1314) but in few words the RichText editor takes the focus and I need to lock it somehow (take advantages of modify callback on JS side does't work because the text carret still show up. I assume it is something inside the Aztec native code that catch and handle click/focus). Take a look at below demo:

Do you know any prop that can lock the Aztec editor ?

Do you know any prop that can lock the Aztec editor ?

I don't think we have such a thing. Did you have chance to look into web implementation? We might be able to get inspiration from there.

I think we should look for something generic that can be applicable to all blocks, like for example putting a transparent view on block.native.js level to prevent taps and removing it when the block is really focused. Not %100 sure how well it'd work but just an idea.