Closed Bug 104633 Opened 24 years ago Closed 24 years ago

Hermes xml content 'blanks out' when re-opened

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 113884

People

(Reporter: roaminglt, Assigned: jst)

References

(
URL
)

Details

I'm really not sure where this bug belongs, or if it is a sidebar issue or an issue with my sidebar tab. 1) visit http://hermes.mozdev.org/installation.html 2) Install hermes 0.2.8 3) View hermes in the sidebar, change to the search tab (or any other tab) 4) Change back to Hermes tab... is is now blank, and will not refresh 'til browser is restarted. I have found that if you go to chrome/hermes/content/hermes.xml and add code to the body onload then all of a sudden this problem is solved. eg: change line 15: <body onload="load();"> to: <body onload="load();alert('debug')"> Then reopen the browser, repeat above steps.. and all works fine. I have searched through my .xml .css and .js files and cannot see what could be wrong.. I can only think that Mozilla is handling something a little awkwardly. files available in the chrome/hermes/content/hermes.* or online at: http://hermes.mozdev.org/src/hermes/hermes/content/hermes.* where * is (xml, css, and js). I cannot understand why adding such an alert would make everything work ok, yet without it the tab blanks out.
Priority: -- → P4
Target Milestone: --- → mozilla0.9.7
Moving to mozilla0.9.8.
Target Milestone: mozilla0.9.7 → mozilla0.9.8
This still occurs in 2001112803 (just to keep up a running commentry) I had been hoping that whatever caused this 'bug' to appear would cause it to also dissapear after time.. but no luck yet. To re-iterate.. this bug did not exist for any previous version before the version of my initial bug report.
Any js console errors reported when you try to reopen your tab?
Using 2001112803 I can't get any console messages when hermes fails to display.
Moving to milestone after mozilla0.9.9 (mozilla1.0 for now).
Target Milestone: mozilla0.9.8 → mozilla1.0
Umm.. isn't there even a chance that someone could at least see what the problem is caused by? So at least a work around can be come up with.
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Oops. Forgot to flag with the nsbeta1+ keyword.
Keywords: nsbeta1+
Target Milestone: mozilla1.0.1 → mozilla1.0
Without wanting to appear as a pest is it possible for this bug to receive some attention to at least work out what is going wrong. Right now I'm not even asking for the issue to be solved.. but just a better understanding of the problem. I'm happy to get together on IRC with someone to demonstrate the bug to anyone with time (I know.. a precious commodity). Seeing this bug on: 2001122408. Oh.. and just to be pedantic I am also seeing this bug on WindowsXP.
Azrael, You have not cited a build ID with your initial bug report. However, you mentioned that "this bug did not exist for any previous version before the version of my initial bug report." Assuming you mean around 2001-10-13, bonsai tells us that the fix for bug 72208 was fixed then. I doubt this has anything to do with the sidebar though. Appears to be an issue with the content itself. (1) Try making the chrome URL to hermes.xml your homepage. (2) Now launch mozilla. (3) Then open a new window. (4) The second window doesn't load hermes.xml. (5) Close the first window. (6) Now reload the second and the content refreshes correctly. Sending over to DOM HTML folks for a look.
Assignee: sgehani → jst
Component: Sidebar → DOM HTML
Keywords: nsbeta1+
Priority: P4 → --
QA Contact: sujay → stummala
Summary: sidebar tab 'blanks out' when re-opened → Hermes xml content 'blanks out' when re-opened
Target Milestone: mozilla1.0 → ---
apologies for not giving a build ID when reporting. the build was from the previous day.. and every build since that day (as far as I can tell) Samir: followed your 6 steps.. and yes I agree with what you see. To anyone else wanting to see this probem.. compare Hermes 0.2.8 to Hermes 0.2.9 version 0.2.9 differs only (as far as this bug is concerned) by having a javascript alert in the onload of the hermes.xml body. This seems to 'bypass' the bug .. however is very annoying. Any DOM HTML people able to advise?
ok, I'll take a look at this.
ok this is a dup of bug 113884, or rather the other way round, but since there is more detailed info there I'll dup this bug there. Azrael, you could provide a better workaround rather than using alert(); you can do document.defaultView.getComputedStyle(document.body,null).getPropertyValue("width"); its kinda long, but it works. basic *** This bug has been marked as a duplicate of 113884 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
grr I keep forgetting that document.body is not implemented for xhtml. Oh well, it gets longer... Azrael put this in your onload: document.defaultView.getComputedStyle(document.documentElement,null).getPropertyValue("width");
Yup kudos fly to basic :)) it works, in build 2002012304 at least - (WinME). The " need to be changed to ' though.. document.defaultView.getComputedStyle(document.documentElement,null).getPropertyValue('width'); Have great days... pete
oh basic you are my gawd!!! :) thanks verifying
Status: RESOLVED → VERIFIED
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.