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

Spec bugs <div> causes page unresponsiveness on mobile #2283

Closed
danieldafoe opened this issue Jan 23, 2017 · 3 comments
Closed

Spec bugs <div> causes page unresponsiveness on mobile #2283

danieldafoe opened this issue Jan 23, 2017 · 3 comments

Comments

@danieldafoe
Copy link

Offending page:
https://html.spec.whatwg.org/multipage/introduction.html#introduction

If I knew where to look to fix this, I would have just opened a pull request.

Description:
When trying to view the spec on mobile, the page does not fit to the viewport. The horizontal scrolling comes from an element that seems to be pushed to the right of the page. The offending element is a div with class .status since it has a right: -9em set on it for devices below 768px in width.

Please refer to the image below for an example using my desktop view and the browser window width being < 768px.

Example:
Screenshot showing Spec bugs div container pushing out of the viewport

@zcorpan
Copy link
Member

zcorpan commented Jan 23, 2017

This was last changed in #2096

The overflowing is intentional. It's not unresponsive -- it responds to viewport changes, it's just overflowing for narrow viewports.

The left edge of the box is visible with initial horizontal scroll position, so you see it's there, and then you can scroll horizontally to see it, or not, if you don't care about it.

(Some tables in the spec are big and will also overflow, btw.)

Is this causing problems?

@danieldafoe
Copy link
Author

Interesting take. Okay, then no problem exists.

However, if that's the intended behaviour, I do believe it's a little strange that if you scroll some way down the page before realizing you can scroll horizontally (and then do so) you see nothing but white. You wouldn't know anything was there unless you were at the top anyway.

That begs the question: why not simply put it back in the normal flow and let it appear under the Introduction heading at all times? What's the purpose of it sitting at that exact position, yet out of flow?

@zcorpan
Copy link
Member

zcorpan commented Jan 23, 2017

Okay, then no problem exists.

Great! Then I'll close this.

The intent is to be unobtrusive yet discoverable and easily accessible. In-flow would hinder reading the spec text, I think.

I'm open to suggestions for changing/improving this, though. Some styles are in this repo and some styles are in https://github.com/whatwg/resources.whatwg.org/blob/master/standard.css

@zcorpan zcorpan closed this as completed Jan 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants