Battlefield.com does not work under edge.

Fixed Issue #8301531

Details

Author
Ben M.
Created
Jul 27, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 29 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Go to https://www.battlefield.com/

Expected: Website shows content
Actual: Website shows black background and nothing else.

Nothing shows on the site, works in all other major browsers.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Christian F.”

  • Same in 14.14395.5.
    Console messages:
    HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier). (XHR)GET - https://www.battlefield.com/source/common/variables.css
    SCRIPT5022: Assertion failed
    webcomponents.min.js (11,1555)

    Debugger message:
    Could not locate https://www.battlefield.com/source/common/variables.css specified in source map https://www.battlefield.com/assets/dist/styles.min.css.map

  • Microsoft Edge Team

    Changed Status to “Fixed”

  • Thanks for the feedback. This appears to have been fixed in 14393.6

    I have attached a screenshot showing how the website appears once you load it up in this build of Edge / Win 10.

    Looking forward to more feedback from you in the future!

    All the best,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

    Changed Status from “Fixed”

    Changed Steps to Reproduce

    Changed Assigned To to “Christian F.”

  • Appears to be related to a NotSupportedError being thrown when document.importNode is called with its deep argument set to false:
    https://jsfiddle.net/9of9eeoj/2/

    By using fiddler to modify webcomponents.min.js used by the Battlefield page, the page can be made to finish loading. Specifically, when the call to document.importNode is modified to pass a true arg for deep import (and the returned node’s children are removed to preserve non-deep behavior), the exception is avoided and the page displays normally.

    The above jsfiddle and Battlefield still fail for me in Edge 39.14901.1000.0

  • This is still broken for me. Latest public build and preview build.

  • Microsoft Edge Team

    Changed Steps to Reproduce

  • It works here on 14393.82 and the jsfiddle says “pass”

  • Microsoft Edge Team

    Changed Status to “Not reproducible”

    Changed Status from “Not reproducible” to “Fixed”

  • We are showing this as fixed on our end now. Thank you all for the feedback. We hope to hear more from you soon.

    All the best,
    The MS Edge Team

You need to sign in to your Microsoft account to add a comment.

Sign in