IE11 and Edge broken with latest release

stramel commented 7 years ago

Description

Please don't hate me for this. I am still digging into it but can say for certain that v0.17.0 serving my build directory works as expected in IE11 and Edge but with v0.18.1 it doesn't. Application is built off the Custom Build version of PSK. (generator-polymer-init-custom-build)

Errors that I am getting:

@font-face failed WOFF integrity check.
No fonts available for @font-face rule
Unable to decode image at URL: 'http://localhost:8081/images/logos/citrix-main.png' with MIME: 'image/png'.
Unable to decode image at URL: 'http://localhost:8081/images/backgrounds/login.jpg' with MIME: 'image/jpeg'.

My multiple CSS background images also seem to be broken now.

I will work on reproduction steps for this.

May be related to #676

Still Broken using polymer build with the following config instead of gulp build.

  "builds": [{
    "bundle": false,
    "js": {"minify": false, "compile": true},
    "css": {"minify": false},
    "html": {"minify": false}
  }]

From looking at it, it appears to be something wrong with polymer serve

Versions & Environment

Polymer CLI: v0.18.1
node: v6.9.1
Operating System: Windows 10

Steps to Reproduce

Expected Results

Actual Results

justinfagnani commented 7 years ago

@stramel I assume that you're serving the built directories with polymer serve since you suspect it. Can you serve with polymer serve --compile-never (after you've build with polymer build)?

stramel commented 7 years ago

@justinfagnani Yes, I am serving the built directory. (polymer serve build/default). Let me check what you just suggested and post back with the results.

justinfagnani commented 7 years ago

Sorry, that should be --compile=never

stramel commented 7 years ago

Updating this thread with what was discussed on Slack for the record.

I tried using an alternative serving tool (http-server) and that worked.

Using @justinfagnani's suggested command polymer serve --compile=never build/default/ -o worked as well.

Not sure how useful this is but after that success, but after that successful serve I tried setting "compile": false in the polymer.json and just using polymer serve build/default -o did not work.

davidmaxwaterman commented 7 years ago

From memory, I would say the option should be --compile never, but I can't find that in the help in v1.0.2 :/ The other options, though, all fit that pattern. IMO, it should be --compile=never or -c never, but polymer-cli doesn't seem to follow the standard (which is a pretty loose standard, admittedly). I'm not sure what is happening, since it should be in the help, right?

srijken commented 7 years ago

We're running into a similar problem with PNG files not working. Appears to be related to the User-Agent header in the GET request. When this is similar to IE11 we get about double the data in the response compared to Chrome User-Agent.

This was tested using Fiddler, so no other variables were changed that might have effect.

Eventually fixed this by installing latest nodejs and latest polymer-cli

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Polymer / tools