Hi All,
Given the responses to this thread (as well as replies only on
public-test-infra), the consensus is to use Github Issues for test bugs
and to use Github labels to identify the related spec (component in
Bugzilla):
https://github.com/w3c/web-platform-tests/issues
As such, I
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24074
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24077
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24079
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
On Jan 2, 2014, at 9:33 AM, John Mellor joh...@google.com wrote:
On Thu, Dec 19, 2013 at 9:32 PM, Maciej Stachowiak m...@apple.com wrote:
On Dec 19, 2013, at 9:02 AM, John Mellor joh...@google.com wrote:
[cross-posted to public-webapps and public-sysapps]
A couple of us from Chrome
On Thursday, December 12, 2013 1:57 PM, Jonas Sicking wrote:
On Thu, Dec 12, 2013 at 1:45 PM, Joel Weinberger j...@chromium.org wrote:
But it would suck if the result is that they create their own form
fields using divs and/or contenteditable.
That's true, although some things like that
