Closed
Bug 41318
Opened 25 years ago
Closed 11 months ago
platform discrepancies with builder.rebuild();
Categories
(Core Graveyard :: RDF, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pete, Assigned: pete)
Details
Attachments
(1 file)
386 bytes,
text/plain
|
Details |
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
Assignee | ||
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
pete: I need a little more to go on here!
Comment 3•25 years ago
|
||
mfuture until more details.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 4•25 years ago
|
||
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...
Assignee | ||
Comment 5•24 years ago
|
||
assigning to myself
Assignee: waterson → petejc
Status: ASSIGNED → NEW
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•24 years ago
|
Target Milestone: Future → mozilla0.9.4
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.4 → mozilla1.0
Comment 6•23 years ago
|
||
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
(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?
Updated•15 years ago
|
QA Contact: nobody → rdf
Updated•11 years ago
|
Target Milestone: mozilla1.0.1 → ---
Updated•7 years ago
|
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.
Description
•