- From: Maritza Johnson <maritzaj@cs.columbia.edu>
- Date: Sun, 17 Feb 2008 15:34:47 -0500
- To: W3 Work Group <public-wsc-wg@w3.org>
- Cc: Rachna Dhamija <rachna@deas.harvard.edu>
- Message-Id: <D48DA941-B9F1-4C95-95BB-F27F285F5328@cs.columbia.edu>
Hi all, This email has two goals: - demonstrate how easy/uninvolved/non-committal a lo-fi protoype can be -- they only took a couple hours - make a suggestion on clarifying what is 'chrome', which we all talked about a lot but I don't think appears much in our rec doc **** I made some changes to the Safari and Firefox 3 chrome that separates the verified content from the non-verified content -- whatever those terms mean, I'm staying out of defining them ... http://www1.cs.columbia.edu/~maritzaj/wsc/chromeMakeover.zip http://www1.cs.columbia.edu/~maritzaj/wsc/ff_favicon.png The zip contains: /chromeMakeover/safari /chromeMakeover/firefox3 In each folder there is an example of how the proposed changes would look on a site with and without SSL. For firefox I also included how the changes might affect Larry (not to be taken as full support for Larry but because it's in firefox 3). The biggest change is the title tag string in now only displayed where the tabs are, the favicon is also only displayed in this area, and there should be a dark line (or whatever else) to signify a distinction between "chrome" and the web content). I moved the SSL lock in Safari from the far upper right hand corner to the favicon location, maintaining the presentation that it's part of chrome, it should be clickable to display the info in the same way. I made these mock-ups last week prior to the release of ff3 beta 3 ... where in the os x version displays the favicon so it looks even more like it's a part of chrome (see picture 1.png attached). In firefox I changed the favicon to a green check mark -- not necessarily a good idea but I needed a place holder. Notice on sites that don't have SSL this area is left empty. I'm not suggesting changes like this are the silver bullet but I'm almost sure we agree that having "trusted" content mixed with untrusted content in the chrome causes problems for users. Thoughts/feedback? -- Maritza http://www.cs.columbia.edu/~maritzaj/
Received on Sunday, 17 February 2008 20:35:11 UTC