Last Comment Bug 340746 - make it possible to disable CSS parsing on iframe-specific basis
: make it possible to disable CSS parsing on iframe-specific basis
Status: NEW
:
Product: Core
Classification: Components
Component: CSS Parsing and Computation (show other bugs)
: Trunk
: All All
: -- enhancement with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks: 343269
  Show dependency treegraph
 
Reported: 2006-06-07 17:21 PDT by Myk Melez [:myk] [@mykmelez]
Modified: 2011-05-04 09:27 PDT (History)
4 users (show)
dbaron: blocking1.9-
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Myk Melez [:myk] [@mykmelez] 2006-06-07 17:21:51 PDT
It'd be useful (for parsing HTML in a hidden iframe never meant to be seen by users) to be able to disable CSS parsing for a specific XUL iframe.  As nsIDocShell has attributes for twiddling plugins, JavaScript, meta-redirects, subframes, and images, perhaps it's the appropriate place to expose a similar attribute for twiddling CSS loading and parsing.
Comment 1 Myk Melez [:myk] [@mykmelez] 2007-01-26 17:36:38 PST
This would be valuable for microsummaries, at least until we have some better way than a hidden iframe for parsing HTML, which we may well get out of bug 361449.
Comment 2 David Baron :dbaron: ⌚️UTC-7 (busy September 14-25) 2007-03-08 18:34:00 PST
Minusing for blocking1.9; hopefully bug 102699 will make it and this will become unnecessary.  This doesn't seem particularly easier than bug 102699, and that's what we really want in the long term.

Note You need to log in before you can comment on or make changes to this bug.