https://bugzilla.wikimedia.org/show_bug.cgi?id=35704

Samuel Bronson <naes...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |naes...@gmail.com

--- Comment #29 from Samuel Bronson <naes...@gmail.com> ---
(Note: This looks like it has changed from being a tracking bug to discussing
what a wikitext version of "<style scoped>" should look like, and how to
implement it.  Also, it doesn't look very mobile-specific anymore to me.)

Personally, I think the simplest approach would be:

  1. Use basically the same syntax as HTML5 does in the wikitext, only without
the first-child restriction. 

  2. *Do* preprocess the style text, I can imagine some rather neat
parameterized templates.  (Catching runaway tags in the page content is
important, of course, but I'm fairly certain this was already the case?)

  3. *Don't* try to do anything complicated to restrict the effects to the
output of one template; it sounds like a lot of work only to make the feature
*less* useful.

  4. Transform the pre-processed scoped CSS in the input into non-scoped CSS in
the output (by generating a class name for each unique scoped stylesheet,
adding that class to the relevant nodes, and appropriately prefixing each
selector), because only Mozilla appears to support the feature by default,
JS-based polyfill only works when JS is on, and you need to sanitize the CSS
anyway.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to