[nikanj]

Messed up js scrolling often means I _can't_ read the actual content. I know WP8 isn't that common, but should I just quietly accept that yet another developer decided to "innovate" and wrote a super sexy scroller that crashes and burns on my browser?

[mrspeaker]

Not quietly, but perhaps just not loudly to everyone around you... an email to the author is a billion times better than another worthless HN comment about color contrast.

[Joeboy]

wrt marginal design choices like colour schemes I absolutely agree, HN people spend too much time bickering about them. But people who wilfully display static content in such a way that people can't see it should be publicly shamed, pour encourager les autres. It's been a solved problem since 1993.

[mwfunk]

Yes, in that forum that may very well be what that means, if the outcome is that everyone ends up bikeshedding about whatever it is that they want to complain about and derailing the entire discussion.

[drcode]

The thing is that we need lots of people to innovate in website design in many different ways if we want the content and technology of the web to get better.

If someone spends months working on a site to incorporate new technology, it's really frustrating if the main feedback is that it breaks scrolling in someone's esoteric preferred web browser.

[tomphoolery]

If the site works well on every device but Windows Phone, then maybe it's not the site that's the problem.

[sequence7]

Although I see your point (Windows Phone is not that popular) couldn't you say the same for any mainstream device? i.e. If the site works well on every device but Linux/iOS/Android it's not the site that's the problem.