Open issues against browsers

[necolas]

The end goal of normalize.css should be to not exist (or realistically, to be extremely small).

This issue is to keep a record of which inconsistencies have been reported as issues at the relevant browser's bug tracker. (Remember to include old closed 'wontfix' issues.) Then we can know when an issue has been resolved and plan to remove it from normalize.css, or if an issue will never be resolved at the browser level.

• create a list of all browser-related issues fixed by normalize.css
• create a list of all "wontfix" issues that normalize.css couldn't, shouldn't, or didn't fix
• open issues on browser bug trackers. Open issue against browser that is the odd-on-out or those not aligned with a spec.
• maintain list of issues opened against browsers and mark them when fixed.

Please help with this effort to list and report issues :)

[sindresorhus]

so much 👍

[sjonnet19]

Awesome

[MarioRicalde]

Great.

May I suggest that we use the GitHub Wiki? If we want some organisation on the wiki we can use GitHub Wikifier.

[Shahor]

Awesome 👍

[maebert]

Great idea. I would appreciate this being in the actual code - that makes it a lot easier to maintain the code and remove obsolete parts.

Another way would be to have individual files for each normalisation, each with a header that describes the normalisation and links to the tracked bug. normalize.css could then be compiled from all files/fixes that have not been resolved on your targeted browsers.

[evandrix]

How about cross-browser inconsistencies? duplicate bug across the affected browsers?

[oemera]

This is a really great idea. Maybe those open bugs/issues should be linked in a wiki article so people can support them to be fixed. If no-one is behind those bugs they won't get fixed.

Is there a bug-tracker for issues/bugs in Internet Explorer? I curious what Microsoft will say to "all" those differencies to other browsers.

[SimonSapin]

The relevant spec is here: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html

When reporting a bug to a browser it helps to point to the part of the spec that they got wrong. But the goal of this spec is also to describe what browsers already do, so if there interop among browsers, the bug might rather be in the spec.

[ahmadalfy]

Kudos

[ramirezj]

Nicholas

Are you planning to tie these bugs to the w3c/web-platform-tests repo on GitHub?

James

[necolas]

Are you planning to tie these bugs to the w3c/web-platform-tests repo on GitHub

Hadn't really thought about it.

[allirense]

I created a page in the wiki with a suggested format for listing browser issues: https://github.com/necolas/normalize.css/wiki/Browser-Issues

[necolas]

Good idea; thanks.

[necolas]

Closing because I don't think anyone filed a single ticket against browsers.