Comments

drobnjak created an issue. See original summary.

miro_dietiker’s picture

The solution for no-javascript could / should be to not display the tabs at all.

drobnjak’s picture

miro_dietiker’s picture

The wrong non-js behavior and proposed change makes these related..

drobnjak’s picture

Title: Improve accessibility of edit perspectives » [META] Edit perspectives user experience
Issue summary: View changes

No-JS behavior will be addressed in the related issue #2862935: Only display tabs if there is a behavior element. However, leaving this issue open for further discussion and eventual problems with accessibility, edit perspectives user experience and to follow-up progress on child issues. Moving issue to META.

miro_dietiker’s picture

Issue summary: View changes

Removing itself from the related task list.
This is a meta, so the typical design is to make the individual tasks children.

smk-ka’s picture

Am I the only one who thinks the current UX of paragraphs behaviors is less than ideal? A typical editor scenario is this:

  1. Editor adds a new paragraph at the very bottom
  2. Now the user has to scroll all the way up to switch to 'behavior' view
  3. Now all the way down again to configure the newly created paragraph's behavior
  4. Now all the way up again to toggle content editing
  5. Now all the way down again to add the next paragraph
  6. WTF?
miro_dietiker’s picture

@smk-ka That's the price you pay with step by step implementation. We divide into small steps that are acceptable because we know we can easily remove the pain points.

The solution to this problem is here, long proposed. But no one considered contributing to getting it done.
#2825581: [META] Introduce a sticky header

johnchque’s picture

@smk-ka we are always open for new features and proposals. :) We also need more patches to get the things done. :)

miro_dietiker’s picture

Issue summary: View changes

Adding the images from the first milestone issue of the original vision for perspective tabs.