Added this to the Later milestone.

Another option is to go all in and make element.style reflect the computed style. This is what jQuery does: http://api.jquery.com/category/manipulation/style-properties/

This comment was originally written by gp7...@gmail.com

Hi,

I would suggest:
1)
To keep known terminology to avoid collisions with standard W3C terminology in the future.
2)
To finish the documentation of the dart:html API and to make at least clear what is Dart specific and what is more or less standard in the W3C world.

I have read this post: http://code.google.com/p/doctype-mirror/wiki/ArticleComputedStyleVsCascadedStyle

As I understand, the computed or "dynamic" style in pixels is not just the information that is statically given in the CSS file or html file.

So I would rather like to have a difference between:

• staticStyle or declaredStyle
• dynamicStyle or computedStyle in pixels

Best regards

This comment was originally written by gp78...@gmail.com

Maybe even a distinction between:

• internalStyle or xmlStyle for the style declared in the HTML element definition.
• externalStyle or cssStyle for the style declared in some CSS block.

This comment was originally written by gp78...@gmail.com

I guess that the Dart team wants to express the CSS and XML information of the DOM in terms of Dart native objects.
Hence it might be useful to have:

• element.xml to get the current XML representation of the element as object.
• element.css to get the static CSS information as object.
• element.style for the complete current style in terms of original expressions like 50% or color "red".
• element.styleAbsolute for the complete current computed style in terms of pixels and RGBA.

See also issue #5048

Added html-api label.

Removed html-api label.

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.