Port bug 1579952 "Mass rename .xul files to .xhtml" to SeaMonkey
Categories
(SeaMonkey :: Build Config, task, P3)
Tracking
(Not tracked)
People
(Reporter: frg, Assigned: frg)
References
(Blocks 1 open bug)
Details
Attachments
(3 files, 3 obsolete files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
text/plain
|
Details |
xul is now xhtml
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Part 1 Mass rename .xul files to .xhtml in suite.
Assignee | ||
Comment 2•5 years ago
|
||
Part 2 Fix references to xul files in suite.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Update from Bill
Assignee | ||
Comment 5•5 years ago
|
||
Now with the right script
Assignee | ||
Comment 6•5 years ago
|
||
Shell script updated with correct bug number
Comment 7•4 years ago
|
||
What is the impact of this change for classic extension support, considering that (a) many abandoned extensions that work with SM <=2.53.x know about specific .xul files (b) extensions that are maintained for PaleMoon etc will continue to do so?
Also, why? Is it just that this rename was done in the FF tree?
Can there be some sort of redirection mechanism? I suppose all supported platform filesystems have link support.
Assignee | ||
Comment 8•4 years ago
|
||
This has no impact on 2.53 and 2.57. Until we release 2.57 this is academic. Then we can discuss later releases based on comm-central which would support web extesnsions only but for now it is a mood point. comm-central is kept building and we are fixing up 2.53 then 2.57 and only then it is decision time.
Comment 9•4 years ago
|
||
Vd
I know it is a pipe-dream now but supporting WebExtensions as well as classic extensions would be a great development.
Description
•