fix(): do not use RegExp lookbehind assertion, not supported in WebKit #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a follow-up fix to anodynos#38. That was my mistake. The regexp lookbehind assertion `(?<!^)` is not supported in some JavaScript engines, esp. WebKit's, and causes error, so it should not be used yet. See - "lookbehind assertions" in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp#browser_compatibility - WebKit issue: [Bug 174931 - Implement RegExp lookbehind assertions](https://bugs.webkit.org/show_bug.cgi?id=174931)
|
It seems WebKit Bug 174931 - Implement RegExp lookbehind assertions is now resolved, so I'm closing it. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up fix to #38.
That was my mistake. The regexp lookbehind assertion
(?<!^)is not supported in some JavaScript engines, esp. WebKit's, and causes error, so it should not be used yet.See: