Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v5 documentation new look and feel (meta bug) #29047

Closed
10 of 12 tasks
patrickhlauke opened this issue Jul 15, 2019 · 9 comments
Closed
10 of 12 tasks

v5 documentation new look and feel (meta bug) #29047

patrickhlauke opened this issue Jul 15, 2019 · 9 comments

Comments

@patrickhlauke
Copy link
Member

patrickhlauke commented Jul 15, 2019

seems #28450 introduced a large number of changes not only to forms, but to the actual look and feel of the v5 version of getbootstrap.com

a few initial problems/issues noted with that (please feel free to add more):

  • contrast in the top navigation bar for the links/icons falls below 4.5:1
  • left-hand navigation scrolling is borked when the nav and page get long (you have to scroll all the way to the end of the content before the left-hand navigation scrolls
  • once the navigation has expand/collapse disclosure widgets, they lack a role="button" and aria-expanded="true"/aria-expanded="false"
  • hover-specific styles for the top nav, breadcrumbs, left-hand navigation, which are not applied on :focus ... so they're all niceties and styles that only work for mouse users, not keyboard users; need doubling up of :hover and :focus styles
  • some changes were introduced to _tables.scss which don't make sense: https://github.com/twbs/bootstrap/pull/28450/files#diff-82ee1ffb694a87db828fe22dcd868aed
  • left-hand navigation also blows up in IE11 - will be fixed in Doc tweaks #29029
  • Move any inline script code to application.js
  • The docs no longer have their toggler so there's no way to navigate the docs on mobile
  • Use our collapse plugin in the sidebar
  • Add transition in the sidebar arrow transform
  • Maybe we should move forms under components since they are components themselves
  • IE11 shrinks the search field
@patrickhlauke
Copy link
Member Author

Screenshot of the v5 left-hand navigation in IE11

Capture

@XhmikosR
Copy link
Member

@MartijnCuppens has made a list too #28450 (comment)

We should consolidate the issues.

Also I have a PR with some fixes for things I noticed #29029

@mdo mdo mentioned this issue Jul 15, 2019
17 tasks
@XhmikosR
Copy link
Member

Updated TODO

@mdo
Copy link
Member

mdo commented Jul 22, 2019

In response to the new todos added:

Add transition in the sidebar arrow tranform

I don't want them transitioning, they should immediately click. Same for using our collapse plugin if that's why folks want—there should be no transition here.

Maybe we should move forms under components since they are components themselves

Negative, forms have so much content and behaviors. I moved them to their own section on purpose.

@XhmikosR
Copy link
Member

For the transitions I don't mind. But we are reinventing the wheel here, because that's exactly why the collapse plugin exists.

As for the forms, IMO the current hierarchy just doesn't make sense. Forms are components themselves. It's just that they have their own components too which is OK.

@ffoodd
Copy link
Member

ffoodd commented Apr 10, 2020

Since:

  1. Collapse plugin is used in sidebar, and the arrow is transitionned
  2. There is a consensus around Forms being outside components;
  3. IE11 is not targetted anymore
  4. aria-expanded is used where appropriate in navigation

I think this one could be closed. Anyone?

@XhmikosR
Copy link
Member

Agreed, @patrickhlauke feel free to reopen if we missed something.

@patrickhlauke
Copy link
Member Author

LGTM (noting though that in IE11 the docs nav is now completely inoperable - but i guess that's clearly signals the "not supporting IE11" angle)

@XhmikosR
Copy link
Member

That's due to JS errors on IE, so yeah.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants