Closed
Bug 78242
Opened 23 years ago
Closed 22 years ago
Display style not working properly
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
People
(Reporter: shivajisus, Assigned: serhunt)
References
()
Details
(Whiteboard: [need input])
The basic idea here is that using tables, divs, or spans to alter and show data
does not work correctly in Mozilla in build ID 2001032319. In IE, the example
works fine. The example on the web page deals with displaying an applet in a
table. Changing some of the applet parameters using javascript works correctly
(toggle hour +1 / -1). However, after the hide/show (using
Display.style="none"), the "toggle hour +1 / -1" button is no longer operable.
This example also fails in Netscape.
Thanking You, Shivkumar Shivaji
Reporter | ||
Updated•23 years ago
|
OS: other → Windows NT
Reporter | ||
Comment 1•23 years ago
|
||
This may have something to do with the browser's internal engine. Is there a
way to do the equivalent of "div" without using the "div" parameter?
Comment 2•23 years ago
|
||
Using today's commercial bits, 2001052504, clicking Togglehour crashes the
browser.
However, I see the problem that you're referring to. Netscape seems to be
destroying the applet (that's what the Java plug-in console says, anyway) and
then reloading it when you display the table again.
Confirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•23 years ago
|
Component: HTMLTables → Plug-ins
Comment 4•22 years ago
|
||
The hide/show issue is resolved, the clock will be redisplayed regardless if you
go forward, backward or stay at the same time. I believe that particular issue
was the result of a fix checked in last week (can't find that bug at the moment
-- but Peter checked in a fix for hidden not functioning correctly).
When the applet is redisplayed, however, it reinstantiates the plug-in. That is
why it returns to the original state. I'm not sure if that is an actual bug though.
AV -- what should happen? Should the applet be redisplayed in the previous
state? Should it still be running in the background and just render? or should
it be reloaded?
Whiteboard: [need input]
If you leave the page and come back it should be reloaded. Whether it tries to
remember and restore its previous state -- depends on the applet. If it uses
savedata mechanism for that, then it will not work, we don't support it yet.
Comment 6•22 years ago
|
||
This is the dredded reframe bug 90268. Plugins are tied to frames and may be
reinstantiated (reframed) from time to time.
*** This bug has been marked as a duplicate of 90268 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 7•22 years ago
|
||
Will fixing bug 90268 solve the problem? i.e. Will we be able to toggle between
style.display="none" and style.display="block" and not reload the applet doing
so? I think that the savedata mechanism should be implemented if possible. My
firm uses the "hide/show" for switching between applet and html view on the
same page. This seems to be the only way to hide information and redisplay it
without using up area (e.g. by using style.visibility="hidden"/"visible"). It
would be great if this can be implemented.
Thanks.
Comment 8•22 years ago
|
||
Yes, this bug will be fixed by bug 90268. Our layout engine creates "frames"
based on CSS. Plugins are tied to frames so their lifetime may not be the same
as the lifetime of their tag.
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•