Closed
Bug 580882
Opened 14 years ago
Closed 14 years ago
Narcissus DOM support
Categories
(Other Applications Graveyard :: Narcissus, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: taustin, Assigned: taustin)
Details
Attachments
(1 file, 4 obsolete files)
48.56 KB,
patch
|
taustin
:
review+
|
Details | Diff | Splinter Review |
Currently, Narcissus does not interact with the DOM. It needs to be updated so that it can be used within a browser.
Assignee | ||
Comment 1•14 years ago
|
||
This patch replaces the global object with a proxy that will reach to the underlying JS engine when needed, allowing it to use browser-specific functions when available. This approach would allow the user to get at the underlying Narcissus constructs. I intend to file a separate bug for that. A number of new unit tests are passing. A few new ones are also failing, mostly due to the 'watch' construct.
Attachment #461304 -
Flags: review?(gal)
Updated•14 years ago
|
Component: JavaScript Engine → Narcissus
Product: Core → Other Applications
QA Contact: general → narcissus
Assignee | ||
Comment 2•14 years ago
|
||
Attachment #461304 -
Attachment is obsolete: true
Attachment #462627 -
Flags: review?(gal)
Attachment #461304 -
Flags: review?(gal)
Comment 3•14 years ago
|
||
Comment on attachment 462627 [details] [diff] [review] Updated patch to work with modularized Narcissus We could wrap the global object with a proxy. What do you think?
Comment 4•14 years ago
|
||
Comment on attachment 462627 [details] [diff] [review] Updated patch to work with modularized Narcissus >diff --git a/js/narcissus/browser.js b/js/narcissus/browser.js >new file mode 100644 >--- /dev/null >+++ b/js/narcissus/browser.js The makefile changes introduced in bug 583281 create symlinks for all files in narcissus/js*.js and the njs script depends on these. Is the Narcissus.browser module only enabled in the browser? Dave
Assignee | ||
Comment 5•14 years ago
|
||
Yup, the browser.js file is only needed for the browser.
Comment 6•14 years ago
|
||
Okay. Our file naming convention is a little goofy, but I guess it's not a big deal. Maybe just add a comment to js/src/shell/Makefile.in explaining that js*.js covers the shell-specific files and only the shell-specific files? Dave
Assignee | ||
Comment 7•14 years ago
|
||
Changes from previous patch: *Redesigned browser.js to rely less on specific names *Renamed browser.js to jsbrowser.js
Attachment #462627 -
Attachment is obsolete: true
Attachment #463013 -
Flags: review?(gal)
Attachment #462627 -
Flags: review?(gal)
Comment 8•14 years ago
|
||
Comment on attachment 463013 [details] [diff] [review] Replacement patch for including browser support Comment style: /* * */ We should ideally not patch the original window object.
Assignee | ||
Comment 9•14 years ago
|
||
Assignee | ||
Comment 10•14 years ago
|
||
The new patch uses a proxy for native code functions. As part of this, the proxy setup has been refactored.
Attachment #463013 -
Attachment is obsolete: true
Attachment #464230 -
Attachment is obsolete: true
Attachment #464285 -
Flags: review?(gal)
Attachment #463013 -
Flags: review?(gal)
Assignee | ||
Comment 11•14 years ago
|
||
Comment on attachment 464285 [details] [diff] [review] Update patch removes need for jsbrowser.js Andreas approved with some changes: * changed 'realGlobal' to 'hostGlobal' * made notes of spidermonkey specific functionality
Attachment #464285 -
Flags: review?(gal) → review+
Assignee | ||
Comment 12•14 years ago
|
||
Changelist: http://hg.mozilla.org/tracemonkey/rev/b5abd91bc7fa
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•