Marcher Technologies Posted November 11, 2011 Posted November 11, 2011 http://community.invisionpower.com/tracker/issue-34470-hardcoded-cke-css/ It is far LESS effort for you to maintain it... and FAR less hell for US to skin it. its ALREADY NOT the CKE..... its already your version of it. why are you allowing 3+extra css files to be called when there is one skin css that can handle it? ipb_ckeditor.css ALL CKE CSS should be here.... Please.
Aisha Posted November 11, 2011 Posted November 11, 2011 Colors should be like languages. Never hard coded.
Marcher Technologies Posted November 11, 2011 Author Posted November 11, 2011 Colors should be like languages. Never hard coded. further the icons should be changeable by skin.............. this would allow that.
Rikki Posted November 12, 2011 Posted November 12, 2011 Putting all CKEditor CSS in one file is simply not practical. For a start, it would involve modifying CKEditor itself, because it expects certain CSS files to exist. Secondly, I believe CKEditor's CSS is more than all of our products' CSS combined - it is not practical to put that in one file, nor would it be helpful. Where important colors need to be moved, though, that's something we're happy to consider.
Mcardle Posted November 12, 2011 Posted November 12, 2011 Putting all CKEditor CSS in one file is simply not practical. For a start, it would involve modifying CKEditor itself, because it expects certain CSS files to exist. Secondly, I believe CKEditor's CSS is more than all of our products' CSS combined - it is not practical to put that in one file, nor would it be helpful. Not practical yes but helpful it certainly would be
Marcher Technologies Posted November 12, 2011 Author Posted November 12, 2011 Putting all CKEditor CSS in one file is simply not practical. For a start, it would involve modifying CKEditor itself, because it expects certain CSS files to exist. Secondly, I believe CKEditor's CSS is more than all of our products' CSS combined - it is not practical to put that in one file, nor would it be helpful. so its better to load up 3+ css files, both third-party and in some cases causing not-https (.....nexus?) warnings because its not in the skin?
Aisha Posted November 12, 2011 Posted November 12, 2011 Putting all CKEditor CSS in one file is simply not practical. For a start, it would involve modifying CKEditor itself, because it expects certain CSS files to exist. Secondly, I believe CKEditor's CSS is more than all of our products' CSS combined - it is not practical to put that in one file, nor would it be helpful. Where important colors need to be moved, though, that's something we're happy to consider.Honestly I think the colors are all anyone is concerned with.
Management Matt Posted November 14, 2011 Management Posted November 14, 2011 You can add your own CSS so that it overwrites the CK Editor defaults if you wanted to. You don't need to wait for us to start the process.
Marcher Technologies Posted November 15, 2011 Author Posted November 15, 2011 You can add your own CSS so that it overwrites the CK Editor defaults if you wanted to. You don't need to wait for us to start the process. Thats not the real issue Matt. its the fact you do not define ipb_ckeditor.css in the skin template to overwrite the cke defaults at stock. Last thing i would ever, ever want to have to manually update when you do the stock is the editorTemplate for CKE. the CKE text area css, without that modification, CANNOT be over-written.... not with all the !important tags in the world.
SubStrider Posted April 15, 2012 Posted April 15, 2012 This is really disappointing. Guess will have to tell the members not to wait for the glaring white editor in the dark skin to be rectified soon if ever.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.