Bug 7765

Summary: hasAttribute always returns false for uppercase attribute names like "STYLE"
Product: WebKit Reporter: Darin Adler <darin>
Component: DOMAssignee: Darin Adler <darin>
Status: RESOLVED FIXED    
Severity: Critical CC: cdumez
Priority: P1 Keywords: InRadar, Regression
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
patch with detailed change log and a layout test ggaren: review+

Darin Adler
Reported 2006-03-14 09:14:41 PST
This is especially important because of a major problem it causes in the Mail application.
Attachments
patch with detailed change log and a layout test (30.07 KB, patch)
2006-03-14 09:28 PST, Darin Adler 		ggaren: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Darin Adler
Comment 1 2006-03-14 09:28:59 PST
Created attachment 7061 [details] patch with detailed change log and a layout test
Darin Adler
Comment 2 2006-03-14 09:29:33 PST
<rdar://problem/4474884> hasAttribute always returns false for uppercase attribute names like "STYLE"
Geoffrey Garen
Comment 3 2006-03-14 09:58:27 PST
Comment on attachment 7061 [details] patch with detailed change log and a layout test The new layout test "console" is neat. "Did not raise an exception as expected" sounds ambiguous to me. I would say, "was expected to raise an exception but didn't" instead. Am I right that lowercasedName is only actually lower case in the HTML case? Maybe we should just call it something like nameCopy instead. r=me
Eric Seidel (no email)
Comment 4 2006-03-14 11:38:03 PST
Comment on attachment 7061 [details] patch with detailed change log and a layout test I find calling your local variable "lowercasedNamed" sorta odd, when half the time it's actually not lowercased. You might consider calling it localName or name depending on which of those is already taken.
Eric Seidel (no email)
Comment 5 2006-03-14 11:38:52 PST
Oops, just call me "ggaren2".
Lucas Forschler
Comment 6 2019-02-06 09:02:31 PST
Mass moving XML DOM bugs to the "DOM" Component.
Note You need to log in before you can comment on or make changes to this bug.