[Webkit-unassigned] [Bug 7492] New: CSS Attribute Selectors fail when the setAttribute() method is used to create an attribute and the attibute name is not Class or ID.

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=7492

           Summary: CSS Attribute Selectors fail when the setAttribute()
                    method is used to create an attribute and the attibute
                    name is not Class or ID.
           Product: WebKit
           Version: 417.x
          Platform: Macintosh
               URL: http://code.clientside.net.au/safari/setAttribute.htm
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: CSS
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: christopher.bentley at gmail.com


Summary:
When an element's attribute is created using the setAttribute() method then
only the attributes named "class" and "id" affect the rendering by associated
CSS Attribute Selector rules. The CSS ignores any other attribute name.

Steps to reproduce:
The page at http://code.clientside.net.au/safari/setAttribute.html demonstrates
the issue.

Expected behaviour:
I expect Safari to style an element using a CSS Attribute Selector when the
attribute has been created using setAttribute() . eg.
setAttribute('title','This is a tooltip') // el[title]

Actual Behaviour:
Only the "class" and "id" attributes affect the CSS rendering of an element
when the attribute is created using the setAttribute() method in Safari.

Workaround:
None found.

Isolation:
Fails on Safari (except with class and id attributes). Firefox 1.5 and Opera
8.5 (Mac) behave as expected.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.