Closed Bug 41318 Opened 25 years ago Closed 11 months ago

platform discrepancies with builder.rebuild();

Categories

(Core Graveyard :: RDF, defect, P3)

x86
FreeBSD
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: pete, Assigned: pete)

Details

Attachments

(1 file)

On browser startup, i have a hook to a function that reads an rdf file from local disk and then builds a menu. It works fine. The data from the rdf file is correctly displayed in the menu. Now if i open a new window from this curently open window, this event will write new data to the rdf file on the local disk. The io write is being done from js. If i then check the generated menu in the new child window, the data is the same data as the parent window. This is fine and is the behavior on unix. However, if i do the same exact thing on windows, the child window's menu has nothing. Each launch of a window calls my function which actually uses builder.rebuild(); On unix it builds with the initial rdf file residing in memory every time. On windows it doesn't build anything. Not even the updated rdf file. It will only build on the initial parent window not it's children. I don't think i can produce a simple test case because there are a lot of things involved. pete
Attached file js function test case
pete: I need a little more to go on here!
mfuture until more details.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
I've run into a similar problem, but I think I can describe it with a simpler test case. About to create a separate bug report...
assigning to myself
Assignee: waterson → petejc
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla1.0
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
tever is not RDF QA anymore
QA Contact: tever → nobody
(In reply to comment #4) > I've run into a similar problem, but I think I can describe it with a simpler > test case. About to create a separate bug report... So what is that bug number?
QA Contact: nobody → rdf
Target Milestone: mozilla1.0.1 → ---
Product: Core → Core Graveyard
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: