[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Federico Grilli updated MAGNOLIA-4411: -------------------------------------- Summary: Main bar looks ugly on IE7 (was: Main bar looks ugly on IE7 and IE8) Environment: IE7 (was: IE7, IE8) Description: Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot. Just for the records, on IE8 and 9 it looks fine. Since we're probably going to need different workarounds for different browsers I think it's wise to start having a look at [GWT's conditional css|https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Conditional_CSS] so that also css, like javascript, is evaluated at compiled-time and a specific version for each browser is produced. One could then write something like, ie {code} @if user.agent ie7 { .myClass { //do horrible workarounds } } @else { .myClass { //do it right } } {code} was: Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot. Just for the records, on IE9 it looks fine. Since we're probably going to need different workarounds for different browsers I think it's wise to start having a look at [GWT's conditional css|https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Conditional_CSS] so that also css, like javascript, is evaluated at compiled-time and a specific version for each browser is produced. One could then write something like, ie {code} @if user.agent ie7 { .myClass { //do horrible workarounds } } @else { .myClass { //do it right } } {code} > Main bar looks ugly on IE7 > -------------------------- > > Key: MAGNOLIA-4411 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4411 > Project: Magnolia > Issue Type: Bug > Security Level: Public > Components: page editor > Affects Versions: 4.5.2 > Environment: IE7 > Reporter: Federico Grilli > Assignee: Federico Grilli > Priority: Major > Fix For: 4.5.3 > > Attachments: GSi7H.png, mainbarontop-IMPROVED.png > > > Just realized this after testing the changes I made for MAGNOLIA-4402 (these > changes have nothing to do with the issue being reported here which has been > verified on current demoauthor.magnolia-cms.com 4.5.2). See attached > screenshot. Just for the records, on IE8 and 9 it looks fine. Since we're > probably going to need different workarounds for different browsers I think > it's wise to start having a look at [GWT's conditional > css|https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Conditional_CSS] > so that also css, like javascript, is evaluated at compiled-time and a > specific version for each browser is produced. One could then write something > like, ie > {code} > @if user.agent ie7 { > .myClass { > //do horrible workarounds > } > } @else { > .myClass { > //do it right > } > } > {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------