Closed
Bug 1491509
Opened 6 years ago
Closed 4 years ago
sectionTemplateExecutionError on viewport-fit MDN page
Categories
(Developer Documentation Graveyard :: CSS, defect, P1)
Developer Documentation Graveyard
CSS
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: esteban, Assigned: e7358d9c)
References
()
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180907104503 Steps to reproduce: Navigating to https://developer.mozilla.org/en-US/docs/Web/CSS/@viewport/viewport-fit will show and report a sectionTemplateExecutionError on macro. Reporting the issue following the troubleshooting KumaScript error guide. Actual results: As the error is present it's not possible to visualize the Formal syntax info, the error reports: Error type: TemplateExecutionError In macro: csssyntax (View Macro) Parsing macro: csssyntax ([u'viewport-fit']) Full text of error: Problem executing template csssyntax: 26 | <h3 id="Formal_syntax">Formal syntax</h3> 27 | 28 | <pre class="syntaxbox">{{csssyntax("viewport-fit")}}</pre> -------------------------------^ 29 | 30 | <h2 id="Accessibility_concerns">Accessibility concerns</h2> TypeError: ejs:1 >> 1| <% 2| /* 3| Displays the syntax of a CSS property or descriptor 4| Cannot read property 'syntax' of undefined at eval (eval at compile (/node_modules/ejs/lib/ejs.js:549:12), <anonymous>:447:61) at returnedFn (/node_modules/ejs/lib/ejs.js:580:17) at /app/lib/kumascript/templates.js:71:26 Expected results: MDN Should have parsed the page correctly displaying the Formal syntax info for the CSS properties.
Comment 1•6 years ago
|
||
Might be fixed by https://github.com/mdn/data/pull/283
Component: KumaScript → CSS
Product: developer.mozilla.org → Developer Documentation
Updated•6 years ago
|
Priority: -- → P1
This will be fixed by https://github.com/mdn/kumascript/pull/802.
Assignee: nobody → e7358d9c
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 3•4 years ago
|
||
https://github.com/mdn/data/pull/283 merged, so closing this one.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•