Skip to content

RegExp bug since angular 2.4.2 #14029

Closed

Description

@hmarchadour

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Since angular 2.4.2, I've a bug on angular bootsrap only on Firefox 31

Expected behavior
The RegExp should not throw a SyntaxError: invalid range in character class error on Firefox 31

Minimal reproduction of the problem with instructions
I've replay a plunker demo according to the pullrequest #13653 that seems introduce this bug.

It's a minimal script that can be reproduce on Firefox 31 according to modules/@angular/compiler/src/selector.ts .

What is the motivation / use case for changing the behavior?
XULRunner 31 (understand a subset of Firefox 31) is the last compatible release supported on Eclipse (Mars/Neon) to embed a Firefox runtime in an Eclipse product.
Firefox 31 works well before angular 2.4.2 with webpack (I don't know with SystemJs).
Actually, angular 2.4.1 is the last compatible release of angular with a embedded Firefox runtime Eclipse product.
Please tell us about your environment:

I've replay this problem only on Firefox 31 (the Operating system does not matter)

  • Angular version: 2.4.2
  • Browser: [ Firefox 31 ]
  • Language: [all]

  • Node (for AoT issues): node --version = does not matter

Activity

  1. hmarchadour commented on Jan 20, 2017

    @hmarchadour
    Author
  2. DzmitryShylovich commented on Jan 20, 2017

    @DzmitryShylovich
    Contributor

    I believe this #13900 will fix it

  3. hmarchadour commented on Jan 23, 2017

    @hmarchadour
    Author
  4. added a commit that references this issue on Jan 24, 2017
    3418cae
  5. added 2 commits that reference this issue on Jan 24, 2017
    b2f9d56
    bd2eecb
  6. added a commit that references this issue on Aug 28, 2017
    1873901
  7. angular-automatic-lock-bot commented on Sep 10, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  8. locked and limited conversation to collaborators on Sep 10, 2019
  9. added a commit that references this issue on Apr 27, 2021
    a49e525
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions