search

XAlandK / paintweb

Automatically exported from code.google.com/p/paintweb
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Investigate scenarios for user interface styling isolation #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently PaintWeb loads an XHTML file which is appended into the 
destination document, and it also adds a reference to a CSS file, for the 
styling of the GUI. This works well when the target application makes 
proper use of CSS. However, it is common that mistakes crop out, and the 
PaintWeb GUI is affected by other style sheets in the application which 
can apply to elements of the PaintWeb interface.

One possible solution is to keep the entire user interface inside an 
iframe. In this iframe the element IDs would no longer need mangling and 
the style sheet could be merged in. The problem is with "floating panels" 
- they'd become stuck inside the iframe.

Another possible solution would be to use scoped styling from HTML 5. I 
need to check which Web browsers implement it (if they do).

Original issue reported on code.google.com by mihai.sucan on 22 Sep 2009 at 11:36

GoogleCodeExporter commented 8 years ago 
As it seems, at the moment no popular Web browser implements scoped styling. 
Additionally, it might not even fit the needs for this task. See:

http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-s
tyle-
element

More investigation is needed.

Original comment by mihai.sucan on 22 Sep 2009 at 12:19