RESOLVED FIXED 3893
-[DOMCSSStyleDeclaration cssText] is not implemented
https://bugs.webkit.org/show_bug.cgi?id=3893
Summary -[DOMCSSStyleDeclaration cssText] is not implemented
Dan Wood
Reported 2005-07-07 11:00:51 PDT
The underlying implementation of -[DOMCSSStyleDeclaration cssText] is not implemented. Test case.... Take a node and ask for its style, then print it out. DOMCSSStyleDeclaration *style = [[self DOMDocument] getComputedStyle:(DOMElement *) node :@""]; NSLog(@"cssText = %@", [style cssText]); Result: ================= ERROR: unimplemented (/Volumes/dwood/dev/WK/WebCore/khtml/css/css_computedstyle.cpp:289 virtual DOM::DOMString DOM::CSSComputedStyleDeclarationImpl::cssText() const) ================= Here is the offending code, in css_computedstyle.cpp: DOMString CSSComputedStyleDeclarationImpl::cssText() const { ERROR("unimplemented"); return DOMString(); }
Attachments
Implement cssText for most rules (9.22 KB, patch)
2005-07-08 21:19 PDT, Anders Carlsson
hyatt: review-
Address comments (9.60 KB, patch)
2005-07-12 03:45 PDT, Anders Carlsson
darin: review+
Anders Carlsson
Comment 1 2005-07-08 21:19:23 PDT
Created attachment 2875 [details] Implement cssText for most rules
Dave Hyatt
Comment 2 2005-07-09 14:11:24 PDT
The cpp file uses namespace DOM so no need for DOM::DOMString there. Can you attach a new patch that minimizes the extra DOM::? Thanks.
Anders Carlsson
Comment 3 2005-07-12 03:45:48 PDT
Created attachment 2921 [details] Address comments
Darin Adler
Comment 4 2005-07-18 07:59:27 PDT
Comment on attachment 2921 [details] Address comments It's a little annoying that CSSComputedStyleDeclarationImpl::cssText returns something with a trailing space. Is there some better way to share the getPropertyName function than putting this extern declaration in the .cpp file? The test looks good to me. I'm going to mark this review+ even though I have those two minor questions/comments above.
mitz
Comment 5 2006-02-18 11:53:33 PST
*** Bug 6359 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.