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

na.leagueoflegends.com - layout is messed up #3645

Closed
webcompat-bot opened this issue Nov 8, 2016 · 12 comments
Closed

na.leagueoflegends.com - layout is messed up #3645

webcompat-bot opened this issue Nov 8, 2016 · 12 comments

Comments

@webcompat-bot
Copy link

URL: http://na.leagueoflegends.com/en/news/game-updates/patch/patch-622-notes
Browser / Version: Firefox Mobile 52.0
Operating System: Android 6.0
Problem type: Layout is messed up

Steps to Reproduce

  1. Navigate to: http://na.leagueoflegends.com/en/news/game-updates/patch/patch-622-notes

Expected Behavior:

Actual Behavior:

Screenshot Description

From webcompat.com with ❤️

@MDTsai
Copy link

MDTsai commented Nov 9, 2016

I can reproduce this issue on Firefox mobile Nightly and Chrome mobile 54. This page is not responsive.

The viewport size is set to device-width:

<meta name="viewport" content="width=device-width">

But body's min-width is 1000px:

html body {
    min-width: 1000px;
}

Looks like Chrome follow viewport width zoom to device-width but Firefox follows min-width.

@wisniewskit
Copy link
Member

wisniewskit commented Nov 9, 2016

It certainly does look like they're using the meta-viewport tag incorrectly. The minimal value they give effectively tells the browser that they will adapt the layout to whatever device orientation and screen-size the user has, but their CSS isn't doing that.

The best thing for them to do here is probably to not mess with the meta-viewport tag at all (just remove it). Then browsers should render the same way Chrome does by default.

If for some user-unfriendly (read: not recommended) reason they want the page to start zoomed-in like Firefox, but still let the user scroll and zoom about themselves, then they need to be specific, since browsers seem to vary in what the default values are. Something like this should do the trick, if memory serves:

<meta name="viewport" content="width=device-width; initial-scale=1; user-scalable=1">

Edit: it would be amusing if they added the tag just to prevent the 300ms tap delay, given that it breaks more than it seems to solve...

@karlcow
Copy link
Member

karlcow commented Nov 10, 2016

<meta name="viewport" content="width=device-width"> should be fine.
I think it's another use case for our viewport issue. On my plate.
whatwg/compat#62

Probably after Tech in Asia, I'll dive into this.

@karlcow
Copy link
Member

karlcow commented Nov 10, 2016

The fact that the site is blown-up and there is the overflow-x

body.riotbar-present {
    margin: 0;
    margin-top: 52px;
    overflow-x: hidden; 
    padding: 0;
    position: relative;
}

means we can't scroll horizontally to see the full content AND (worse) we can't zoom out. That's probably the most important issue.

Removing the overflow-x: hidden would go a long way in making it more usable. To note that we can zoom-in, just not zoom-out.

@adamopenweb
Copy link
Collaborator

Their Twitter seems to be one way communication only: https://twitter.com/LeagueOfLegends

But @RiotGames is on Github. Maybe @Neamar or @clifferson can help us find a contact to get this fixed?

@Neamar
Copy link

Neamar commented Nov 14, 2016

Hey guys, just acknowledging the issue for now. I can probably give more context on this tomorrow :-)

@Neamar
Copy link

Neamar commented Nov 15, 2016

Ok, thanks for the report, that's definitely an issue.

As you've noticed, the current website is not responsive -- however, the bug you mention has already been fixed in our internal environments. It's part of a bigger package, so deployment may take some time while we ensure all teams are happy with the changes, but within a couple weeks this bug should be fixed!

@wisniewskit
Copy link
Member

Thanks for the update, @Neamar!

@Neamar
Copy link

Neamar commented Dec 15, 2016

Hi there,

The fix is ready to go live, however it's likely not going to be pushed to prod before january. I'll be back with more news soon, sorry for the delay

@adamopenweb
Copy link
Collaborator

@Neamar that's great, thank you!

@Neamar
Copy link

Neamar commented Jan 4, 2017

This should now be fixed!

@adamopenweb
Copy link
Collaborator

Looks great, thanks for your help @Neamar! 😀
Closing this as fixed.

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

6 participants