Skip to main content
Meta Stack Exchange

Return to Answer

Accuracy edit, the syntax/features are implemented in a Javascript engine
Source Link
dylan-myers
dylan-myers
  • 248
  • 1
  • 5

Stack Overflow states their support for browsers here:

Stack Overflow supports the last two stable versions of major browsers. This does not include beta/dev releases, which are not supported.

Therefore it is unlikely these 'issues' will be fixed. You mention that the dev team have generously fixed previous issues only occuring on old browsers, but dbc's answer gives clues as to why these changes aren't the same. The optional chaining syntax cannot be polyfilled unlike previous issues which are generally caused by new features (which can be polyfilled.)

Additionally, on SE's JavaScript migration post, optional chaining has previously been mentioned with no response from SE.

With these blockers in mind, the only way to mitigate these issues is either for SE to restrict the syntax they use for a sliver of users or for these users to update their browsers. There may be a fork of the Firefox version you mention that implements a JavaScript engine that supports ES6 features like optional chaining, but I am not aware of any.

Stack Overflow states their support for browsers here:

Stack Overflow supports the last two stable versions of major browsers. This does not include beta/dev releases, which are not supported.

Therefore it is unlikely these 'issues' will be fixed. You mention that the dev team have generously fixed previous issues only occuring on old browsers, but dbc's answer gives clues as to why these changes aren't the same. The optional chaining syntax cannot be polyfilled unlike previous issues which are generally caused by new features (which can be polyfilled.)

Additionally, on SE's JavaScript migration post, optional chaining has previously been mentioned with no response from SE.

With these blockers in mind, the only way to mitigate these issues is either for SE to restrict the syntax they use for a sliver of users or for these users to update their browsers. There may be a fork of the Firefox version you mention that implements ES6 features like optional chaining, but I am not aware of any.

Stack Overflow states their support for browsers here:

Stack Overflow supports the last two stable versions of major browsers. This does not include beta/dev releases, which are not supported.

Therefore it is unlikely these 'issues' will be fixed. You mention that the dev team have generously fixed previous issues only occuring on old browsers, but dbc's answer gives clues as to why these changes aren't the same. The optional chaining syntax cannot be polyfilled unlike previous issues which are generally caused by new features (which can be polyfilled.)

Additionally, on SE's JavaScript migration post, optional chaining has previously been mentioned with no response from SE.

With these blockers in mind, the only way to mitigate these issues is either for SE to restrict the syntax they use for a sliver of users or for these users to update their browsers. There may be a fork of the Firefox version you mention that implements a JavaScript engine that supports ES6 features like optional chaining, but I am not aware of any.

Source Link
dylan-myers
dylan-myers
  • 248
  • 1
  • 5

Stack Overflow states their support for browsers here:

Stack Overflow supports the last two stable versions of major browsers. This does not include beta/dev releases, which are not supported.

Therefore it is unlikely these 'issues' will be fixed. You mention that the dev team have generously fixed previous issues only occuring on old browsers, but dbc's answer gives clues as to why these changes aren't the same. The optional chaining syntax cannot be polyfilled unlike previous issues which are generally caused by new features (which can be polyfilled.)

Additionally, on SE's JavaScript migration post, optional chaining has previously been mentioned with no response from SE.

With these blockers in mind, the only way to mitigate these issues is either for SE to restrict the syntax they use for a sliver of users or for these users to update their browsers. There may be a fork of the Firefox version you mention that implements ES6 features like optional chaining, but I am not aware of any.