Hello all
After switching from tables (with the exception of one or two inheritted from Actinic) we have finally got our site to display cross browser as we wish it to.
Below are a few of the issues we encountered along the way that may help others when attempting the switch to a css layout outside of actinic themes. Feel free to use or disregard as you wish . This is not an exhaustive list, just some of the points we faced, if you have any additions that we did not encounter I would be happy to see those too.
1 Absolute positioning - use with caution as this was one of the key reasons our site was bursting it width controls. We worked around this with controlled margin placement and clearall declarations
2 Hidden overflow & z indexing - worked as it should until 'innerlayout' was added. For some reason it would not render correctly in FF or Opera irrespective of what changes were applied. We have removed this and use fluid centre settings (as most would do me thinks) and fixed left/right content columns.
3 Text display - we found that the solution to unpredicatable text was to completely overwrite the Actinic css and this resolved all issues. Making sure tthat control sheets were all saved into site1 and referenced with the full URL.
4 Background images - as point 3
Does not look too many but rest assured, they took sometime to resolve.
I hope you find these useful and as stated, please feel free to add to these comment. I can now state we have a 99% non-act css site that renders and runs with Actinic without issue.
And finally, if you wish to showcase your site why not add it into our promote your site section in the community centre (link in sig), only rule is that it must be Actinic driven.
Kind Regards
After switching from tables (with the exception of one or two inheritted from Actinic) we have finally got our site to display cross browser as we wish it to.
Below are a few of the issues we encountered along the way that may help others when attempting the switch to a css layout outside of actinic themes. Feel free to use or disregard as you wish . This is not an exhaustive list, just some of the points we faced, if you have any additions that we did not encounter I would be happy to see those too.
1 Absolute positioning - use with caution as this was one of the key reasons our site was bursting it width controls. We worked around this with controlled margin placement and clearall declarations
2 Hidden overflow & z indexing - worked as it should until 'innerlayout' was added. For some reason it would not render correctly in FF or Opera irrespective of what changes were applied. We have removed this and use fluid centre settings (as most would do me thinks) and fixed left/right content columns.
3 Text display - we found that the solution to unpredicatable text was to completely overwrite the Actinic css and this resolved all issues. Making sure tthat control sheets were all saved into site1 and referenced with the full URL.
4 Background images - as point 3
Does not look too many but rest assured, they took sometime to resolve.
I hope you find these useful and as stated, please feel free to add to these comment. I can now state we have a 99% non-act css site that renders and runs with Actinic without issue.
And finally, if you wish to showcase your site why not add it into our promote your site section in the community centre (link in sig), only rule is that it must be Actinic driven.
Kind Regards
Comment