I read the closed issue re: browser support (http://drupal.org/node/1974054) and it stated that the them should render in IE8 but not necessarily look as good. It also mentioned that the responsive layout does not work. Based on this, I have a few questions and items to note:

  1. I have checked "Media query support for IE6-8". This should take care of the responsive layout problem in IE, correct?
  2. Search box renders really bad. It appears to work, but you can see below how bad it displays
  3. Username, logout and settings links display incorrectly
  4. The menu is left justified, rather than right justified
  5. Blocks that should be in the right sidebar appear below the content. This occurs regardless of which page I am viewing
  6. The filter buttons to select a particular Content Type display in a vertical list, rather than buttons at the top

screenshot

These appear to be more than just not looking as good.

CommentFileSizeAuthor
commons_ie8.jpg30.42 KBAnonymous (not verified)
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Zarabadoo’s picture

Status: Active » Postponed (maintainer needs more info)

I have checked "Media query support for IE6-8". This should take care of the responsive layout problem in IE, correct?

You can enable this feature, and it works to a certain extend, it is not supported. The idea is that responsive is typically a method of layout for smaller screens. Considering IE8 is not something you find on many portable devices, there is not a lot of focus towards getting it to work that way. Yes, it is cool to be able to resize the screen and have the layout dynamically change. Considering the only time such a thing gets used on a desktop is when us web folks constantly resize our window to marvel at the dynamically changing layout. That reasoning is why we figure our time is better spent pursuing other fixes and features.

In the end, I am actually trying to lighten the theme and make it less complicated. Don't be surprised if some of the settings added by Adaptive are removed in pursuit of this. With how heavily this is designed to focus on specific features, it really limits how much flexibility we can allow.

  1. Search box renders really bad. It appears to work, but you can see below how bad it displays
  2. Username, logout and settings links display incorrectly
  3. The menu is left justified, rather than right justified
  4. Blocks that should be in the right sidebar appear below the content. This occurs regardless of which page I am viewing
  5. The filter buttons to select a particular Content Type display in a vertical list, rather than buttons at the top

I am actually unable to reproduce these issues with IE8. I can get something similar with IE7, but IE8 seems to be acting as expected. Is there any more information you can give me about the environment you are viewing this in? (OS version, if you have compatibility mode on, if the site is being viewed in actual IE8 and not the emulated view.)

Anonymous’s picture

Status: Postponed (maintainer needs more info) » Active

Zarabadoo,
Thank you very much for the reply. For the first part, then, are you saying it would be best to NOT use the responsive features at all? Or, that this will be addressed in the future?

As for the platform...Windows XP SP3 Build 2600. IE 8.0.6001.18702.

Zarabadoo’s picture

I would suggest not using it as there is no attention being put in that direction nor is it planned.

Anonymous’s picture

Zarabadoo,
I am trying the CSS3PIE module and currently have the rounded corners and shadows working but entering the selectors that were in the globals.style.css file for radius. Do you think this might be an option for IE8 support?

Anonymous’s picture

We have fixed the problem with the front page (anonymous). We had to change the % of the columns to 30% for IE, rather than 33.33%. We put this code in the lt-ie9.css file. Now looking up the other pages to see what needs to be done.

Zarabadoo’s picture

It is not something that we will include. We are taking the progressive enhancement approach. Things like gradients, rounded corners and shadows will not show in unsupported browsers with a default install. Those are design flourishes and so subtle that they will not bring extra usability, so it is not worth the extra complexity or weight. The only thing we try to be on the lookout for is if thinks look illegible or the layout is broken.

That said, feel free to use the CSS3PIE module if you wish. We will not be attacking any bugs caused by it, though.

Anonymous’s picture

Understand. I will continue to post what we have to do to enhance the Commons theme in IE8, just in case anyone needs the info. Believe me...I wish our company would just upgrade to Win7-IE9/10 or let me use the Google Chrome Frame Plugin. Would be SO much easier.

Zarabadoo’s picture

This commit should keep new installs from falling into compatibility mode and help the problem a little bit.

http://drupalcode.org/project/commons_origins.git/commit/bf79db6

It is basically setting the chrome/edge and clear type settings to "On" in the commons_origins theme settings. There are still other issues related directly to the XP version of IE8 that don't seem to be showing on later versions of the OS. I am still seeing what can be done with them at the moment.

Anonymous’s picture

For anyone else wondering, we have had to make a few tweaks to make the pages display properly. The following is what was added to the lt-ie9.css file. We are still working on the Menu Bar/Search Bar, as it is pushing the search way below the Header region:

/*
Fix the ANONYMOUS front page only displaying 2 columns
*/

.two-33-66 > .region-two-33-66-first, .two-66-33 > .region-two-66-33-second, .three-3x33 > .region, .five-5x20 > .panel-row > .region, .three-inset-right > .inset-wrapper > div.region-three-inset-right-inset, .three-inset-left > .inset-wrapper > div.region-three-inset-left-inset {
width: 30%;
}

/*
Fix the LOGGED IN front page only displaying 2 columns
*/

.two-33-66 > .region-two-33-66-second, .two-66-33 > .region-two-66-33-first, .three-inset-right > .inset-wrapper > div.region-three-inset-right-middle, .three-inset-left > .inset-wrapper > div.region-three-inset-left-middle {
width: 65%;
}

/*
Fix the white boxes in Content Display
*/

.commons-pod, .page-user .pane-views-panes .block-inner, .commons-pod-comments .comment-wrapper, .front.not-logged-in .pane-views-panes > div, .front.not-logged-in .pane-views > div, .front.not-logged-in body.page-node .pane-views-panes > div, .page-events .view-commons-events-upcoming .view-content, .pane-commons-bw-group > .block-inner, .view-display-id-commons_events_upcoming_page .views-row article, .view-commons-groups-directory > .view-content > .views-row > .node-teaser, .view-commons-groups-directory > .view-content > .views-row form, .view-commons-groups-directory > .view-filters > .node-teaser, .view-commons-groups-directory > .view-filters form, .view-commons-homepage-content .node-teaser.node-group > .view-content > .views-row > .node-teaser, .view-commons-homepage-content .node-teaser.node-group > .view-content > .views-row form, .view-commons-homepage-content .node-teaser.node-group > .view-filters > .node-teaser, .view-commons-homepage-content .node-teaser.node-group > .view-filters form, body.front.logged-in #views-exposed-form-commons-homepage-content-panel-pane-1 .views-exposed-widgets.widgets-active, .page-events .region-three-25-50-25-third .pane-views-panes .block-inner, .pane-search-result .block-content .search-results, .page-search-user .user-results {
padding: 14px;
}

/*
Fix Contributors display on What's Going On? page
*/
.views-view-grid td {
padding: 3px;
}

Zarabadoo’s picture

Status: Active » Fixed

This should also help with getting IE8 up to snuff. There is one other niggle with the group search, but I am going to attack that in a separate ticket as it needs help in all browsers.

http://drupalcode.org/project/commons_origins.git/commit/06cf568

I am not experiencing all of the issues @gr8britton is seeing with panel widths, unfortunately. I have looked in XP IE8 and Windows 7 IE8 and just can't seem to recreate them with the latest set of commits. So for now, I am marking this one as fixed. I am sure there will be others, but those can be tackled with some new issues.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.