qiye.163.com - see bug description

[MDTsai]

URL: http://qiye.163.com/
Browser / Version: Firefox 49.0
Operating System: Mac OS X 10.11
Problem type: Something else - I'll add details below

Steps to Reproduce

1. Navigate to: http://qiye.163.com/
2. scroll down to "buy users" area

Expected Behavior:
Should be one line

Actual Behavior:
Last character is in next line

Works fine in Chrome 51 and Safari 9.1.2

From webcompat.com with ❤️

[karlcow]

Thanks @MDTsai

The user-agent stylesheet for the input element

• in Safari (WebKit) border-width: 2px and display: inline-block
• in Opera (Blink) border-width: 2px and display: inline-block
• in Firefox (Gecko) border-width: 3px and display: inline

Testing with a simple html page with only an input element.

• Left: WebKit/Blink
• Right: Gecko

Once we set the default value to 2px it fixes the issue.

Two possible actions:

1. Convince them to add rule for input element so that it is fixed at 2px.
2. Change the Gecko user-agent stylesheet. (I did it in the past I can do it again)

Switching to needscontact, but will probably close as duplicate of a bugzilla bug if we decide to go with option 2. I'll prepare a patch if yes.

At least according to the default CSS in CSS2, we are wrong for the value of the input for display

input, select { display: inline-block }

Now the funny game is that, how many sites do we break if we change the default value that some people might have compensated for. 📎

@miketaylr @denschub @adamopenweb @MDTsai opinions?

[miketaylr]

Convince them to add rule for input element so that it is fixed at 2px.

This seems like the safest option, in that it won't unintentionally break/regress other sites' layout.

If someone wanted to do some kind of analysis to see if a local build with this new border-width broke top sites, that would be interesting.

[karlcow]

@MDTsai the ball is in your camp. If you could find a contact and all them to add the rule.
Thanks.

[MDTsai]

OK, try to reach them today!

[karlcow]

@MDTsai did you get any contacts?

The company behind 163 is NetEase
https://en.wikipedia.org/wiki/NetEase

And Probably people contributing to @NetEase could help us find the right person for fixing this front-end issue.

@bingohuang Maybe can help us.

[MDTsai]

@karlcow Customer service of 163.com said they can't reproduce on their side, so they can't help on this.

[karlcow]

hehe. I wonder what they tested. It's reproducible perfectly.

[MDTsai]

Ping @andrewleo and @lucyking if they can share some connection to 163.com

[lucyking]

Many thanks for the reporting && exhaustive analysis. I have left NetEase already,but I will try to convey this bug to the Email Department.

[reinhart1010]

It seems that this issue is fixed.