Closed
Bug 793497
Opened 13 years ago
Closed 11 years ago
Alternate method to using inline script required for page
Categories
(developer.mozilla.org Graveyard :: General, defect)
developer.mozilla.org Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: trevorhemail-mozbug, Unassigned)
Details
(Whiteboard: [type:feature])
This page https://developer.mozilla.org/en-US/docs/XUL/Property/editable uses an inline script to display the Fx_minversion_inline template if the page path ends in XUL/menulist, so when included in this page https://developer.mozilla.org/en-US/docs/XUL/menulist it should show the template.
An alternative needs to be implemented.
Several sub pages of https://developer.mozilla.org/en-US/docs/XUL/textbox do a similar thing with a slightly different script {{ page.unprefixedpath == 'XUL:textbox' ? web.html(' ' .. template.Fx_minversion_inline(3)) : '' }}
Updated•13 years ago
|
Whiteboard: feature request;
Updated•13 years ago
|
Whiteboard: feature request; → [type:feature]
Updated•12 years ago
|
Flags: needinfo?(dwalsh)
Comment 2•12 years ago
|
||
This logic should be within a template, right? We really shouldn't be muddling our docs with ternary code; the least amount of template features in the documents themselves, the better.
I think Les would agree.
Flags: needinfo?(dwalsh) → needinfo?(lorchard)
Comment 3•12 years ago
|
||
Yeah, kumascript does not & will not support expressions like this in docs. That kind of logic needs to be written in JS code in a macro template. Basically, the only valid syntax in docs is a simple macro like {{ name(args) }}
Flags: needinfo?(lorchard)
Comment 4•11 years ago
|
||
Is the underlying issue (pages trying to use inline script) still happening anywhere? I don't know of any.
Comment 5•11 years ago
|
||
I'm going to WONTFIX unless it is still happening, in which case please reopen...
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•