890855 - False KumaScript errors being cached

Status: RESOLVED DUPLICATE of bug 866458

(developer.mozilla.org Graveyard :: KumaScript, defect)

Description

[Adrian Aichner [:anaran]]

What did you do?
================
1. Edit https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function, fixing typos
2. Add revision comment "fixing typos"
3. Save

What happened?
==============
scripting errors about mdn.localString

What should have happened?
==========================
No scripting errors

Is there anything else we should know?
======================================

Comment 1

[John Karahalis [:openjck]]

Sheppy, is this something that can be corrected on the writing side? Please bump back to MDN product if not.

Comment 2

[Eric Shepherd [:sheppy]]

This has been happening a lot lately. There are no issues on the writing side. We seem to be getting bogus errors cached by KumaScript. A force refresh resolves the issue, but these errors should not be getting cached.

There is no scripting error, even; but errors get reported anyway, until the force refresh.

Comment 3

[Adrian Aichner [:anaran]]

Correct, CTRL+SHIFT+R fixes the problem for me too, this time in canary Google Chrome.

Comment 4

[Eric Shepherd [:sheppy]]

This is frightening away contributors, by the way, and is happening really frequently when editing pages that use macros. Can we prioritize this?

Comment 5

[Jean-Yves Perrier [:teoli]]

I think this is a duplicate of bug 866459.

Separate them again if I'm wrong.