View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003778 | MMW v4 | Documentation | public | 2007-10-17 15:56 | 2009-02-12 09:58 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | suspended | ||
Product Version | 3.0 | ||||
Summary | 0003778: Some MM2 scripts stop MM3 from starting | ||||
Description | MM2 scripts can prevent MM3 from starting. To solve this, we need a way to prevent such scripts from being loaded into MM3. perhaps the best way would be by indicating in each script a 'compatible MM version' line. e.g. MM version: 3.0.0.0 - 3.1.0.0 If this line is missing then the script wouldn't run in MM 3. Or if the script indicated a version not bounded by the compatible versions, then it wouldn't run. Note: If we do this, we'd need to think about how to prevent users from continually having to re-install scripts with each new version. Perhaps best would be to only use x.y instead of x.y.z.zz. e.g. MM version: 3.0 - 3.9 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
There are several problems. First of all, script author never knows in which versions will his script work well, this can be indicated only for older versions. I'm not sure how e.g. Firefox handles this, as far as I know they specify somewhere which script is compatible with which versions. Then, this issue is mostly about MM2 scripts running under MM3. Since they don't have any such specification, the only real solution would probably be to change their extension (e.g. not to use VBS, but something like MSC). However, I'm not sure that this is the best idea, particularly at this moment... |
|
Yes--firefox includes information within the script metadata that describes the versions of firefox that the script is compatible with. Perhaps we should add this for MM 3.1 to the spec. Better yet--we should add it to the spec now, but only implement the support in MM for 3.1. |
|
Let's try to do it together with the web scripting repository... |
|
Resolving for now, let's review it as soon as we have the scripting repository. |