when I change href of a <link "css"> with setAttribute, colors is ok but not <div> position.

RESOLVED WORKSFORME

Status

()

Core
Layout
RESOLVED WORKSFORME
14 years ago
13 years ago

People

(Reporter: mozillabug, Unassigned)

Tracking

({qawanted})

Trunk
x86
All
qawanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment, 1 obsolete attachment)

788 bytes, text/html
Details
(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; fr-FR; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; fr-FR; rv:1.6) Gecko/20040113

In the page at
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/setAttribute_css.html,
when you change listbox value from "bleu foncé" to "beige foncé", it's ok.
But if you change to "cadre jaune", the positions of <div> are not following.   

Reproducible: Always
Steps to Reproduce:
1.open :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/setAttribute_css.html
2.change "CSS :" listbox to "cadre jaune"


Actual Results:  
the position of the <div> they are not good

Expected Results:  
the position of the <div> change like the color of the new css

note: the probleme is solved when I begin to use mousegesture.
thank you
This bug could use a minimal testcase.
Depends on: 175364
Keywords: qawanted
Summary: when I change href of a <link "css"> with setAttribute, colors is ok but not <div> position. → when I change href of a <link "css"> with setAttribute, colors is ok but not <div> position.
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> This bug could use a minimal testcase.

What ? :/
Exactly what I said.  It would be easier to determine what's going on given a
page with absolutely the smallest amount of HTML and CSS necessary to reproduce
the bug.
Assignee: dbaron → nobody
Component: Style System (CSS) → Layout
QA Contact: ian → core.layout

Comment 4

14 years ago
I see this on LInux 2004050306. "cadre jaune" is not the only one that causes
this.  It seems to happen randomly.
OS: Windows ME → All

Comment 5

13 years ago
Created attachment 151467 [details]
Testcase

This is a very strange bug.  All the elements in the testcase are required to
reproduce the problem.

Updated

13 years ago
No longer depends on: 175364
What is this testcase supposed to do that it's not doing now?

Comment 7

13 years ago
Created attachment 151494 [details]
Better testcase

This version has some added descriptive text.
Attachment #151467 - Attachment is obsolete: true
So.. the testcases in this bug workforme as far as I can tell.

So does the site, though it may be that I'm missing a problem there -- there's a
lot of noise and comment 0 doesn't actually specify what the problem is.

Comment 9

13 years ago
Just checked; WFM in current builds.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 10

13 years ago
Ok, I'll explain again.
When I load this page :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/setAttribute_css.html

I have this :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/step1.png
It's ok.

When I choose "cadre jaune" in the popup-menu, i have that :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/step2.png
the positions of the divs are not good.

But when i try to make a mousegesture i have that :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/step3.png
the positions become well, like the file "res/cadrejaune.css" say.

Idem when, at this stage, i try to choose "beige foncé" :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/step4.png

And, with mousegesture :
http://leiopar.free.fr/DISKETTE/bug_gecko/setAttribute_css/step5.png

note : Now I ave Mozilla 1.7 and FireFox 0.9
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---

Comment 11

13 years ago
It doesn't work in 1.7; however, it works in current builds. Try something more
recent than 1.7 (like a recent nightly; download at
http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/).
(Reporter)

Comment 12

13 years ago
Ok !
With Mozilla 1.8 bug is down !
So... 
Thank you to everyone who develop Mozilla !
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago13 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.