Bug 8673 - CSS edited with JS ".style" property not updated
Summary: CSS edited with JS ".style" property not updated
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://dimitri008.elitehostlive.com/
Keywords: NeedsReduction
Depends on:
Blocks:
 
Reported: 2006-04-30 18:00 PDT by Dimitri Bouniol
Modified: 2006-11-26 04:29 PST (History)
3 users (show)

See Also:


Attachments
Bug in Action (45.68 KB, image/png)
2006-04-30 18:15 PDT, Dimitri Bouniol
no flags Details
works for me (242 bytes, text/html)
2006-11-26 04:27 PST, Alexey Proskuryakov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitri Bouniol 2006-04-30 18:00:36 PDT
HTML that was created with JavaScript and edited using the JavaScript style property will not change after being edited a second time.
For the url, click on the Log In link in the red sidebar, the click the link again. You should notice that the second time, several elements are not visible. The alert tells you the opacity of one of the nodes. You may find the node in the web inspector by typing "meNameBox" in the Web Inspector search box.
Comment 1 Dimitri Bouniol 2006-04-30 18:15:17 PDT
Created attachment 8046 [details]
Bug in Action

First box shows first click on the link, second box shows the effect after clicking the second time.
The alert box is the same both times.
The web inspector says that the opacity is 1 the first time, and 0 the second time.
Comment 2 Dimitri Bouniol 2006-05-31 00:45:57 PDT
Note: The opacity value appears in the status bar instead of an alert.
Comment 3 Mark Rowe (bdash) 2006-07-08 04:14:28 PDT
Dimitri, the URL provided does not seem to be accessible at present.  Can you please attach the problematic page to this bug report?
Comment 4 Alexey Proskuryakov 2006-11-26 04:27:56 PST
Created attachment 11634 [details]
works for me

I have tried to re-create the problem, but my tests worked as expected.
Comment 5 Alexey Proskuryakov 2006-11-26 04:29:18 PST
The bug URL is still inaccessible, so closing as INVALID. Please re-open with a reproducible test.