RE: Adding a warning to Working Drafts pointing to Editor's Drafts

Everett:  Do you believe the proposed warning is accessible as you requested?
http://lists.w3.org/Archives/Public/public-html/2010Oct/0458.html 

Laura:  Do you still want to text in the warning changed from "looks at" to "refer to"?
http://lists.w3.org/Archives/Public/public-html/2010Oct/0466.html

If you still have concerns I suggest you file bugs for these possible changes.

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: public-html-request@w3.org [mailto:public-html-request@w3.org] On Behalf Of Maciej Stachowiak
Sent: Tuesday, November 02, 2010 11:00 AM
To: Julian Reschke
Cc: HTML WG
Subject: Re: Adding a warning to Working Drafts pointing to Editor's Drafts


On Nov 2, 2010, at 9:14 AM, Julian Reschke wrote:

> On 01.11.2010 16:33, Paul Cotton wrote:
>> The latest messages on this thread occurred very early on Fri AM ET and I have been travelling across 9 time zones to the TPAC meetings ever since.  This is my first chance to give my view on this item.
>> 
>>> It seems the general sentiment is in favor of a warning that shows up no matter where you are in the draft, but can be hidden to avoid distraction.
>> 
>> It is not obvious to me that we have a concrete change proposal to take action on here.  Does the WG actually agree that a problem exists?  Will any warning be user suppressable or not?   How exactly will the warning be implemented and what user agents will it work on?  Will suppressing the warning be done in an "accessible" way?
>> 
>> In our private dialogue with the HTML5 Editor the Chairs explained why we wanted the warning he added to the Working Draft removed:
>> 
>>> If the existing text is buggy, we ask that such be reported publicly, and discussed openly, giving everybody an opportunity to participate.
>> 
>> Following the above sentiment, I would prefer that we not rush to judgment here and that we use our WG Decision Policy to determine the WG's position on this matter and any actions to be taken.
>> 
>> Therefore I would like to suggest that someone file a bug that clearly states the rationale for needing a warning in Working Drafts on the TR page hopefully with a detailed change proposal that describes how the warning will be implemented so that we can use the WG's Decision Policy to decide how to act on the bug.
>> 
>> /paulc
> 
> In the meantime, there's a new warning in. It appears to use absolute positioning over the actual text, which considerably slows down my UA, and also interacts badly with in-text search (where the highlighted text may not be visible anymore because it's under the warning message).
> 
> Can we *please* stop messing with the readability?
> 
> Also: why does this message appear on the *editor's* draft, and recommends reading the very same???

I believe the idea is to get something set up for a new round of Working Drafts, and then remove it once again.

We still have a few days of publication moratorium to go, so let's make sure to take the opportunity to give feedback and refine the message. I filed the following bug:

"Please add a way to hide the Working Draft warning"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11196

If I get the concurrence of my co-chairs, I'll promote that to a pre-LC bug. In any case, I would request that the editor address it before we publish.

Julian, what UA do you use? I'll file a separate bug about the slowness if I can reproduce it. I did not see a perf issue in Safari.

Regards,
Maciej

Received on Tuesday, 2 November 2010 10:49:38 UTC