Open
Bug 1862626
Opened 8 months ago
Updated 5 months ago
`xsl:sort`: `case-order` is not respected for strings
Categories
(Core :: XSLT, defect, P2)
Core
XSLT
Tracking
()
People
(Reporter: canadahonk, Assigned: canadahonk)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
No description provided.
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Summary: `xsl:sort`'s `order` and `case-order` was broken → `xsl:sort`'s `order` and `case-order` is not respected
Assignee | ||
Updated•8 months ago
|
Summary: `xsl:sort`'s `order` and `case-order` is not respected → `xsl:sort` order` and `case-order` is not respected
Assignee | ||
Updated•8 months ago
|
Summary: `xsl:sort` order` and `case-order` is not respected → `xsl:sort`: `order` and `case-order` is not respected
Assignee | ||
Updated•8 months ago
|
Summary: `xsl:sort`: `order` and `case-order` is not respected → `xsl:sort`: `order` and `case-order` is not respected for strings
Assignee | ||
Comment 1•8 months ago
|
||
Actually I think we do respect order
, just not case-order
.
Summary: `xsl:sort`: `order` and `case-order` is not respected for strings → `xsl:sort`: `case-order` is not respected for strings
Assignee | ||
Comment 2•8 months ago
|
||
Assignee | ||
Updated•8 months ago
|
Assignee: nobody → omedhurst
Status: NEW → ASSIGNED
Comment 3•8 months ago
|
||
Set release status flags based on info from the regressing bug 1719550
status-firefox119:
--- → affected
status-firefox120:
--- → affected
status-firefox121:
--- → affected
status-firefox-esr115:
--- → affected
Updated•8 months ago
|
Updated•8 months ago
|
Severity: -- → S3
Priority: -- → P2
Updated•7 months ago
|
Attachment #9361595 -
Attachment description: Bug 1862626 - Respect case-order for XSLT string sorting → WIP: Bug 1862626 - Respect case-order for XSLT string sorting
Comment 4•7 months ago
|
||
Set release status flags based on info from the regressing bug 1719550
status-firefox122:
--- → affected
Updated•7 months ago
|
Updated•5 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•