1386448 - Experiment and its extension won't be reload, unless/even restart the browser

Status: RESOLVED DUPLICATE of bug 1783667

(WebExtensions :: General, defect, P5)

Description

[YF (Yang)]

Prerequisites:
Take https://github.com/aswan/webext-experiment-hello as the example.


STR 1:
1. Artificially create an error, like modify the "type": "function" to "type": "string" in experiment/schema.json
2. Load the experiment and the extension in about:debugging#addons, you see it won't work and "TypeError: this.parameters is undefined  Schemas.jsm:2073:1" in Browser Console.
3. Correct this error in experiment/schema.json
4. Reload the experiment and the extension, you still see the error and won't work.

p.s. In actual case, I does the opposite operation, i.e. correct error and reload them, then check the correctness, the reload won't work misleading and confusing developers to still has same error.


STR 2:
1~3 see the above.
4. "Remove" both in about:debugging#addons.
5. re-load the experiment and the extension, you still see the error and won't work.


Actual results:
1. The error message is same, the source code is updated but does not take effect (see them via moz-extension:// path, somecases you can access it from error messages - file).


Expected results:
1. The experiment or extension was correctly reloaded when it was Reload.

Comment 1

[YF (Yang)]

p.s. I don't know about its etiology and component, WebExtensions: Experiments (here) or Developer Tools: about:debugging.

Comment 2

[YF (Yang)]

I see sometimes the experimental source code will not be updated (when running and in Debugger) even if the browser is closed and restart (I'm sure not just closed the window). Unexpected caching?

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 4

[Rob Wu [:robwu]]

The experiments implementation has been updated since this bug was filed.

I have enumerated all potential ways of encountering caching issues in bug 1783667.
Since the specific example linked above doesn't work any more (it's a rdf-based experiment), I'll close this in favor of bug 1783667.