Skip to content

Kibana doesn't load in IE #31693

Description

@flash1293

Current Kibana master doesn't load in IE due to some react-intl related error
screenshot_2019-02-20_at_11 12 11

6.7, 7.0 and 7.x do work though.

@Bamieh

Activity

  1. added
    bugFixes for quality problems that affect the customer experience
    on Feb 21, 2019
  2. snide commented on Feb 21, 2019

    @snide
    Contributor

    cc @elastic/kibana-qa and @elastic/kibana-design so they are aware.

  3. chandlerprall commented on Feb 21, 2019

    @chandlerprall
    Contributor

    I reproduced in IE11 locally against master

    packages/kbn-i18n/node_modules/react-intl/lib/index.js
    Line 165, Column: 5

    maps to the 2nd line of

      if (typeof Symbol === "function" && Symbol.asyncIterator) {
        AsyncGenerator.prototype[Symbol.asyncIterator] = function () {
          return this;
        };
      }
    

    Running this in the IE11 console creates the same error:

    thing = function() {};
    thing.prototype[Symbol.asyncIterator]
    
  4. added
    Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//
    on Feb 22, 2019
  5. elasticmachine commented on Feb 22, 2019

    @elasticmachine
    Contributor

    Pinging @elastic/kibana-platform

  6. chandlerprall commented on Feb 22, 2019

    @chandlerprall
    Contributor

    bisecting commits through git, appears to be 3727b53 #29072 which introduces the change breaking IE11.

    Moving before that commit there is an existing error in IE11 about a SyntaxError: Expected ';' from ./node_modules/vega-lib/build/vega.js in vendors.bundle.dll.js, so there may be a few issues to resolve for IE support.

  7. flash1293 commented on Feb 22, 2019

    @flash1293
    ContributorAuthor

    @chandlerprall The vega issue gets resolved with 562edd6
    so that shouldn't pop up again if the problem with 3727b53 #29072 gets resolved (at least it works in the PR branch flash1293:fix/vega-version which was based on a commit prior to 3727b53). If this shouldn't be the case, please ping me.

    For testing: Cherry-picking 562edd6 on top of the commit before 3727b53 should work if there isn't a third IE breaking change at the same time.

  8. chandlerprall commented on Feb 22, 2019

    @chandlerprall
    Contributor

    Specifically, adding "@storybook/react": "^4.0.7", to x-pack's package.json triggers the error. There is a release note on 4.1.6 that it includes an IE11 fix, bumping to that version removes the error but still no pageload happens (stays on a blank screen).

    Adding the @storybook/react dependency duplicates or triplicates a number of babel-related packages in yarn.lock (all with miniscule version differences) so that's where I'm looking now. It might be best to remove the storybook dependencies for now to get master working again. @clintandrewhall

  9. flash1293 commented on Feb 24, 2019

    @flash1293
    ContributorAuthor

    I talked to @mistic about this while trying to fix the vega problem, and it might be possible to resolve this by configuring webpack to correctly compile this stuff down to IE supported syntax (packages/kbn-babel-preset). If we find a reliable way to prevent this, #31413 should get a lot easier.

    For now it makes more sense to just revert though IMHO, no idea how easy it is to resolve this once and for all without unwanted side effects (like killing compile performance)

  10. cchaos commented on Mar 4, 2019

    @cchaos
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Project:i18nTeam:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//bugFixes for quality problems that affect the customer experience

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions