Open Bug 1611647 Opened 4 years ago Updated 9 months ago

Port bug 1579952 "Mass rename .xul files to .xhtml" to SeaMonkey

Categories

(SeaMonkey :: Build Config, task, P3)

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: frg, Assigned: frg)

References

(Blocks 1 open bug)

Details

Attachments

(3 files, 3 obsolete files)

xul is now xhtml

No longer depends on: 1454023, 1431050
Assignee: nobody → frgrahl

Part 1 Mass rename .xul files to .xhtml in suite.

Part 2 Fix references to xul files in suite.

Status: NEW → ASSIGNED
Attached file Shell script used for the renames (obsolete) —
Attached file Shell script used for the renames V2 (obsolete) —

Update from Bill

Attachment #9123097 - Attachment is obsolete: true
Attached file Shell script used for the renames V2 (obsolete) —

Now with the right script

Attachment #9123100 - Attachment is obsolete: true

Shell script updated with correct bug number

Attachment #9123104 - Attachment is obsolete: true
Depends on: 1441668
Depends on: 1684878

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.

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.

Vd

I know it is a pipe-dream now but supporting WebExtensions as well as classic extensions would be a great development.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: