Skip to content
This repository has been archived by the owner on Dec 10, 2021. It is now read-only.

RND-476 add ie9 support #630

Merged
merged 1 commit into from
Nov 18, 2016
Merged

RND-476 add ie9 support #630

merged 1 commit into from
Nov 18, 2016

Conversation

gusliedke
Copy link
Contributor

https://jira.comicrelief.com/browse/RND-476

IE 9 CSS limitation by preventing more than 4095 selectors in a CSS file.

I'm surprised drupal 8 doesn't deal with it by default .. haven't found much documentation about it.

There is this module https://www.drupal.org/project/advagg but it's quite big with too many settings. It works but when you split the stylesheet it should add those files in a condition to only load on IE9 not in all browsers.

I've added the condition in the html template manually, used http://blesscss.com/ to split the stylesheet and committed the CSS files. This is only used by IE9 .. so we don't need to worry too much about it. This is a temp solution to test the issue.

Please let me know if you have other solutions!

@gusliedke
Copy link
Contributor Author

@pvhee @bimsonz @Saphyel @Heleen-cr @AndyEPhipps .. if you have an idea how to tackle it in drupal 8.

@Saphyel
Copy link
Contributor

Saphyel commented Nov 15, 2016

@gusliedke @pvhee I found this... but I didn't test it:
http://www.bradwade.com/drupal8/D8-disable-css-aggregation/

@gusliedke
Copy link
Contributor Author

@Saphyel gonna give it a try

@gusliedke
Copy link
Contributor Author

Disable css aggregation is good to not include a stylesheet in drupal core aggregation. But it doesn't split the stylesheet in different files to fix IE9 bug.

@gusliedke
Copy link
Contributor Author

@pvhee If we don't have other solution I think we should push this code .. it will only affect IE9. And I will create a documentation about it.

@pvhee
Copy link
Contributor

pvhee commented Nov 18, 2016

@gusliedke can you provide documentation on this and/or discuss with @AndyEPhipps @Heleen-cr so they're able to follow the same splitting? Then it's OK for me to go in without the use of a D8 module

The only thing I'd like to see still is some discussion on d.o. talking about this problem and proposing a solution, we can't be the only ones having these issues

@pvhee
Copy link
Contributor

pvhee commented Nov 18, 2016

Maybe @Saphyel or @bimsonz can help dig something up (see ^^)

@gusliedke
Copy link
Contributor Author

Not many big sites in drupal 8 that supports ie9 I guess .. https://www.unicef.es/ has same issue ie9

@gusliedke
Copy link
Contributor Author

ie9 and ie8 are both < 1% traffic .. we don't need to maintain this fix for much time .. people will not invest time to sort this out.

Copy link
Contributor

@pvhee pvhee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gusliedke cool, let's get this merged then if QA approved.

@Saphyel
Copy link
Contributor

Saphyel commented Nov 18, 2016

MS does no longer support 10 or older version since a year... why do we have to provide support to a insecure and legacy browser when even the owner give up at them?

@pvhee pvhee merged commit b828e71 into develop Nov 18, 2016
@pvhee pvhee deleted the feature/RND-476_ie9_issue branch November 18, 2016 17:12
@AndyEPhipps
Copy link
Contributor

@Saphyel because of our users, innit

@Saphyel Saphyel mentioned this pull request Nov 22, 2016
@pvhee pvhee mentioned this pull request Jan 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants