Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
IE 11 vs preProcessedHeaders.split(/\r?\n/) #748
Comments
|
The regular expression works for me in a newer patch version of IE 11, so this might be a bug in the older version Browserstack seems to be using.
|
|
Thank you for having taken the time to test! More tests from more people are welcome here, as it is nearly impossible to obtain information about IE11 builds market shares. |
|
I'm running into the same thing on the newer version of IE 11 that was posted.
|
|
@charlesbjohnson your version is exactly the same as mine. Edit: or do you simply confirm that you run into this issue too? |
Confirming that I'm running into this issue on the same version that you posted. I don't know how to confirm if this is the latest IE 11, but I downloaded it today from here. |
|
Correction: My version is the same as @dgraham's (here), and not the version @pierremanceaux originally posted in the PR description. |
|
Yeah, didn't find a way to confirm the build date either, but for everything I see, seems pretty recent to me, if not the last one. I would bet it is the last one because:
Seems like something is broken in IE11's last build... |
|
@pierremanceaux I use a newer version it seems, see image.
Cant reproduce your problem but still have the problem in fetch:
|
|
Interesting @ansbar , so in your version, |
|
@dgraham maybe we should re-open this issue? |
|
preProcessedHeaders.split(/\r?\n/) works with your examples but not in my real life test. |
This comment was marked as spam.
This comment was marked as spam.
Gjøres pga følgende issues; github/fetch#750 github/fetch#748 zloirock/core-js#751 zloirock/core-js#741 I bunn og grunn, core-js@^3.6.0 introduserte støtte for String.prototype.split med regex som har sticky-flag. Pga bug her så fungerer ikke funksjonen som forventet noe mer i eldre IE11 versjoner. E.g `"test".split(/e/) === ['t', 'e', 's', 't']`, denne burde gitt `['t', 'st']`
|
The core-js ticket isn't getting any progress right now. Is there a way to work around this issue by not using the polyfilled regex and doing it a different way? |
|
This project does not use core-js at all, the issue you are seeing is one from core-js itself I believe and not something in this project. |
|
@JakeChampion we do know of the issue though and it's common to use core-js polyfills and this polyfill. If we can use different code that doesn't trigger the bug - surely that's a win? |
I'm happy to accept a pull-request for that change |
Hello devs, and thank you for this great polyfill.
I am facing a strange bug in IE 11 (on Browserstack, no access to and old Windows system).
In short, the behaviour of preProcessedHeaders.split(/\r?\n/).forEach(...) seem to be inconsistent between for instance Chrome's last version (my reference point) and IE11 on Browserstack.
IE 11 -> Incorrect
Chrome -> Correct
Meaning that the polyfill simply doesn't work for me on IE 11.
If you want to try yourself assuming you have an access to an IE 11 browser:
Is anyone able to reproduce this?
Thank you for your time in advance.
Note
Polyfill version: 3.0.0
Here is the IE11 build I tested with: