Closed Bug 665730 Opened 14 years ago Closed 13 years ago

Kuma: CSS embedding

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect, P1)

Product:
developer.mozilla.org Graveyard
Component:
Wiki pages
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: openjck, Unassigned)

References

Details

(Whiteboard: u=user c=wiki s=2012-06-05 p=)

No description provided.
Version: unspecified → Kuma
Assignee: lcrouch → nobody
Target Milestone: 1.0 alpha → ---
Priority: -- → P1
Blocks: 710720
Whiteboard: [u: user] [c: wiki] → [u: user] [c: wiki] s=2012-06-05
Whiteboard: [u: user] [c: wiki] s=2012-06-05 → u:user c:wiki s=2012-06-05 p=
Would bug 665730 cover this?
Fail. That should be bug 665735. We might be able to kill a few birds with one stone by doing it.
I see no way that a JSFiddle-like feature (with all the complexity of the integration into the wiki UI, point where we didn't even brainstorm seriously on what we want) could be ready for Kuma-launch. We need a way to embed CSS for July launch. We have 100 of pages relying on the ability to embed CSS.
Don't worry, Jean-Yves, we have the same goal in mind. I thought doing this all through jsFiddle might speed things up for the team, but if not we certainly don't need to go that route.
I wonder though - if we allow iframes in wiki content, doc authors could embed jsfiddles already ... they would be externally hosted, but it's the easy hacky way to do it. Do we allow iframes in wiki content?
Whiteboard: u:user c:wiki s=2012-06-05 p= → u=user c=wiki s=2012-06-05 p=
Superseded by other bugs. New bugs should be filed against the existing code sample functionality.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Version: Kuma → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.