Google Mail Buttons not respecting native look
Hi, I was about to file a bug regarding the way the "Archive", "Delete" and "Report Spam" buttons are rendered in the GMail pages by Safari. Then I decided I had better try a small test case with a page that contained: <form> <input form="submit"> <input form="button"> </form> and found the buttons rendered fine. Can anyone work out whether this is a 'bug' or something particular that Gmail is doing? I tried using the DOM inspector in Firefox (it is a bit more advanced that Safari's) to see if I could notice anything in particular, but I am not seeing it. Andre
GMail is using the HTML 4 <button> tag. Safari 2.0 renders these with a generic look. WebKit TOT/nightly renders them with a native look unless the site styles them with CSS. <BUTTON type="button" class="ab" id="ac_rc_^i" style="font- weight:bold">Archive</BUTTON> — Timothy Hatcher On Jan 28, 2006, at 11:47 PM, André-John Mas wrote:
Hi,
I was about to file a bug regarding the way the "Archive", "Delete" and "Report Spam" buttons are rendered in the GMail pages by Safari. Then I decided I had better try a small test case with a page that contained:
<form> <input form="submit"> <input form="button"> </form>
and found the buttons rendered fine. Can anyone work out whether this is a 'bug' or something particular that Gmail is doing?
I tried using the DOM inspector in Firefox (it is a bit more advanced that Safari's) to see if I could notice anything in particular, but I am not seeing it.
Andre _______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
Out of curiosity, what features do you find missing from the WebKit DOM inspector (in the nightly)? This is different from the Safari DOM inspector in the debug menu. http://webkit.opendarwin.org/blog/?p=41 — Timothy Hatcher On Jan 28, 2006, at 11:47 PM, André-John Mas wrote:
I tried using the DOM inspector in Firefox (it is a bit more advanced that Safari's)
I was using the one in the debug menu, in the release edition. I will take a look at the one you referenced. The Firefox DOM Inspector doesn't stop at the current document. It allows you to descend into iFrames, which the one in the Debug menu doesn't do. It also allows you to see the CSS attributes and the Javascript model of the document. I'll take a look at the nightly. Andre On 29-Jan-06, at 03:35 , Timothy Hatcher wrote:
Out of curiosity, what features do you find missing from the WebKit DOM inspector (in the nightly)?
This is different from the Safari DOM inspector in the debug menu.
http://webkit.opendarwin.org/blog/?p=41
— Timothy Hatcher
On Jan 28, 2006, at 11:47 PM, André-John Mas wrote:
I tried using the DOM inspector in Firefox (it is a bit more advanced that Safari's)
participants (2)
-
André-John Mas
-
Timothy Hatcher