- From: Alan Stearns <stearns@adobe.com>
- Date: Fri, 26 Jun 2015 15:28:34 +0000
- To: Ivan Herman <ivan@w3.org>, Dave Cramer <dauwhe@gmail.com>
- CC: W3C Digital Publishing IG <public-digipub-ig@w3.org>
On 6/26/15, 2:19 AM, "Ivan Herman" <ivan@w3.org> wrote: > >> On 25 Jun 2015, at 18:11 , Dave Cramer <dauwhe@gmail.com> wrote: >> >> >> >> B.t.w. [3] and [4] seems to be the right bug report areas for Firefox >>and Chrome, respectively. I do not know what the rules are to submit new >>reports… >> >> Generally there are detailed guidelines provided. For example, [A] >>provides guidance on writing bugs on WebKit, [B] for Mozilla, [C] for >>Blink, and [D] for IE. >> >> Note that filing a bug on a browser is even scarier than sending an >>email to www-style! I've only done one [E], and it was an adventure. > >Sigh. I must admit I was afraid of that… I’m happy to help anyone with trepidations about filing browser bugs. It is a bit more work than sending an email, but it has to be done if there are incompatibilities to fix. I usually know someone to ping to get some attention focused on a bug report. I can also help anyone interested in adding test cases to W3C test suites. That can be a longer-term, more permanent way of keeping browsers (and other user agents) from going off-track. Thanks, Alan > >> >> Cheers, >> >> Dave >> >> >> [A] http://www.webkit.org/quality/bugwriting.html >> [B] >>https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guideline >>s >> [C] https://www.chromium.org/for-testers/bug-reporting-guidelines >> [D] >>http://blog.reybango.com/2013/02/28/submitting-an-internet-explorer-bug-t >>o-microsoft/ >> [E] https://bugs.webkit.org/show_bug.cgi?id=139667 >> >> >> [1] http://j.mp/1IzWL5D >> [2] http://w3c.github.io/typography/ >> [3] https://bugzilla.mozilla.org/buglist.cgi?quicksearch=addHitRegion >> [4] http://j.mp/1RxQZ9c
Received on Friday, 26 June 2015 15:29:13 UTC