Closed
Bug 1603157
Opened 5 years ago
Closed 3 years ago
Stop using nsIVariant in XSLTProcessor
Categories
(Core :: XSLT, defect, P3)
Core
XSLT
Tracking
()
RESOLVED
FIXED
100 Branch
| Tracking | Status | |
|---|---|---|
| firefox100 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: peterv)
Details
Attachments
(1 file, 1 obsolete file)
XPCVariant, as far as I can tell, can't represent all JS values. In particular, it treats Symbol values as undefined. So it's not a good tool for "store an arbitrary value"..
I assume there's no particular spec for this thing?
|
||
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:peterv, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(peterv)
|
Assignee | |
Updated•5 years ago
|
Flags: needinfo?(peterv)
Priority: -- → P3
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
|
Assignee | |
Comment 3•3 years ago
|
||
Depends on D140363
|
|
Assignee | |
Updated•3 years ago
|
Assignee: nobody → peterv
Status: NEW → ASSIGNED
|
||
Updated•3 years ago
|
Attachment #9266537 -
Attachment description: WIP: Bug 1603157 - Stop using nsIVariant for XSLTProcessor.getParameter/setParameter. → Bug 1603157 - Stop using nsIVariant for XSLTProcessor.getParameter/setParameter. r?smaug!
|
|
||
Updated•3 years ago
|
Attachment #9266536 -
Attachment is obsolete: true
Pushed by pvanderbeken@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0c7799adddfa
Stop using nsIVariant for XSLTProcessor.getParameter/setParameter. r=smaug
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•