Changes between Initial Version and Version 1 of Ticket #5047, comment 7
- Timestamp:
- Apr 17, 2012, 10:13:27 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5047, comment 7
initial v1 1 1 I have made a mistake writing in may last post 2 > >"it will take" - notice the " marks3 > >it has more to do with not agreeing on skin design2 >"it will take" - notice the " marks 3 >it has more to do with not agreeing on skin design 4 4 Let's say it's true but it gave a false impression you have described below: 5 [[BR]][[BR]] 5 6 6 7 >As if the contents.css says something thats not true. [[BR]] 7 > >if it doesn't change anything and it's decided by your skin design?8 **It does say true.* It changes the editor's **body** color to transparent but the problem is that other elements that are **placed behind** this body are not transparent.8 >if it doesn't change anything and it's decided by your skin design? 9 **It does say true.** It changes the editor's **body** color to transparent but the problem is that other elements that are **placed behind** this body are not transparent. 9 10 10 11 E.g. Window glass is transparent but if you put red board behind it, it will no longer look transparent but red. This is what is happening here. 11 12 12 > >I see couple of ways to solve this, make that line in contents.css work as advertised or remove it.13 >I see couple of ways to solve this, make that line in contents.css work as advertised or remove it. 13 14 We can't use one rule on elements it was not assigned to. Once again this works and will not be changed - perhaps adding few comment lines warning about elements behind editor's body would solve the issue here. 14 15