Hi Adam,
The editors draft has been updated with the items from our last emails:
http://www.w3.org/2006/WSC/drafts/rec/rewrite.html
Please raise any additional issues by November 27. Thanks.
Mez
Hi Adam,
It's too bad you didn't CC me on the discussion because I think you
misunderstood several of my points.
Thanks. We've actually discussed your emails in meetings. I'm glad you've
cleared up our misunderstanding.
Then what are you taking about? I've attached two screen shots of
Dear Adam Barth ,
The Web Security Context Working Group has reviewed the comments you sent
[1] on the Last Call Working Draft [2] of the Web Security Context: User
Interface Guidelines published on 26 Feb 2009. Thank you for having taken
the time to review the document and to send us comments!
mzu...@us.ibm.com wrote:
We are changing 7.4.3 to:
User agents often include features that enable Web content to update
the user's bookmark file, e.g. through a JavaScript API. If
permitted unchecked, these features can serve to confuse users by,
e.g., placing a bookmark that goes
Comments below.
Web user agents MUST prevent web content from obscuring, hiding, or disabling
security user interfaces.
This is impossible in a multi-window web user agent in an overlapping
window manager (e.g., every major browser on every major
general-purpose operating system).
Web user
All,
The Web Security Context Working Group asked WebApps to review
Section 7.4 of their Web Security Context Working Group spec:
http://www.w3.org/TR/wsc-ui/#robustness-apis
If you have any comments, please send to the following list by
September 24 at the latest:
The title of the spec is actually Web Security Context: User
Interface Guidelines:
http://www.w3.org/TR/wsc-ui/#robustness-api
On Sep 17, 2009, at 1:57 PM, Barstow Art (Nokia-CIC/Boston) wrote:
All,
The Web Security Context Working Group asked WebApps to review
Section 7.4 of their Web
