Opened 13 years ago
Closed 13 years ago
#7545 closed bug (worksforme)
Hide/show on a table row fails for Firefox in certain cases
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | |
Component: | effects | Version: | 1.4.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Hiding a row, attaching it to the DOM, then showing it causes the display to be set to "block" for Firefox (which is bad, since it then causes the row to show in the first column only).
(Tested on Firefox 3.6.10)
Change History (5)
comment:1 follow-up: 2 Changed 13 years ago by
Component: | unfiled → effects |
---|---|
Milestone: | 1.5 |
Owner: | set to Peter Crabtree <peter.crabtree@…> |
Priority: | undecided → low |
Status: | new → pending |
comment:2 follow-up: 3 Changed 13 years ago by
Status: | pending → new |
---|
Replying to rwaldron:
http://jsfiddle.net/rwaldron/Nqfa4/5/
Can you confirm this is the behavior you were expecting?
In Firefox 3.6.10, that adds two rows, unless I have FireBug open, in which case it adds one. :-/
The intended behavior is to add a hidden row, and then show it (in a real-world application, the showing part would happen later).
comment:3 Changed 13 years ago by
Status: | new → pending |
---|
Replying to Peter Crabtree <peter.crabtree@…>:
Replying to rwaldron:
http://jsfiddle.net/rwaldron/Nqfa4/5/
Can you confirm this is the behavior you were expecting?
In Firefox 3.6.10, that adds two rows, unless I have FireBug open, in which case it adds one. :-/
The intended behavior is to add a hidden row, and then show it (in a real-world application, the showing part would happen later).
That's only because console is undefined and the js is run twice. Try http://jsfiddle.net/Nqfa4/6/
Can you can confirm that's the behavior you want?
comment:5 Changed 13 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Ok then. http://jsfiddle.net/jitter/Nqfa4/7/
Thanks for taking the time to contribute to the jQuery project.
If you feel this ticket was incorrectly closed feel free to report back and reopen the issue.
Please take a look at this:
http://jsfiddle.net/rwaldron/Nqfa4/5/
Can you confirm this is the behavior you were expecting?