283541 - Style changes via nsIDOMCSSStyleSheet don't work on cells in nsXULTreeBuilder populated trees

Status: RESOLVED EXPIRED

(Core :: XUL, defect)

Description

[Andrew Miller]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041231
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041231

If you create a tree from an RDF datasource, and then attempt to manipulate the
stylesheet dynamically using nsIDOMCSSStyleSheet, either by setCSSText on an
existing rule, or by deleting a rule and readding another rule with the same
name, the style of the tree does not update, even after a call to
tree.builder.reload().

If the user clicks to sort the tree on a column, the style jumps between the new
and old styles as it is sorted. This only affects the first stylesheet change,
and subsequent ones never take effect.


Reproducible: Always

Steps to Reproduce:
1. Create a XUL document with a tree in it. Set up a Javascript that will find
the tree, and then insert a new stylesheet rule into the document using the
::-moz-tree-cell(propname) { background-color: red; } syntax(where
properties="propname" is an attribute on the tree).
2. Delete the rule, and add a new one with a different background colour.
3. Confirm that the rule in the stylesheet representation is the correct one.
Actual Results:  
The background colour is the old background colour(red in the example above).

Expected Results:  
The background colour should have been changed in response to the manipulation
of the stylesheet DOM.

Comment 1

[Boris Zbarsky [:bzbarsky]]

I think we have existing bugs on the tree's style context cache mess...

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.