Closed Bug 1930033 Opened 1 year ago Closed 1 year ago

comic-days.com, Expanding product lists does not work on Firefox.

Categories

(Web Compatibility :: Site Reports, defect)

Desktop
Windows 11
defect

Tracking

(firefox134 fixed)

RESOLVED WORKSFORME
Tracking Status
firefox134 --- fixed

People

(Reporter: alice0775, Unassigned)

References

Details

Expanding product lists does not work on Firefox.

Steps to reproduce:

  1. Open https://comic-days.com/#days-original-thursday
  2. Click on もっと見る (37作品) v (English translation:View More 37ptoducts) at the bottom of this section

Actual results:
Nothing happens.
Error console shows the following error:

Uncaught SyntaxError: illegal character U+30FB                    2368-4f051732b0717037.js:1:5784

The error occurs the following javascript code .
... m={オリジナル:n,新人・読切:e,総合:a} ...

Expected results:
The rest of the products should be displayed.

Fixed range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=838b6676e282adf1df0e291e4bc8109e0467f5a3&tochange=6d6ee1c2471701a7ecc056d807cbbff12bd7fb8e

The site seems to have been fixed. The source code now looks like:

let c=r?MangaScroll5column:RankingGrid,m={オリジナル:n,"新人・読切":e,総合:a},d={};

Notice that "新人・読切" is now enclosed in quotes.

Also I'm confused why this a regression from bug 1927706, because bug 1927706 should have actually allowed to run the original source without quotes.

Evaluating ({オリジナル:0,新人・読切:0,総合:0}) in current release reports Uncaught SyntaxError: illegal character U+30FB, whereas with bug 1927706 applied, that code snippet runs successfully. That's because before the update to ICU 76 we were still using Unicode 15, but ICU 76 updated to Unicode 16 and U+30FB (KATAKANA MIDDLE DOT) was added to ID_Continue in Unicode 15.1.

Confirmed the bug was fixed. I can no longer reproduce the ssue on 128esr, 132.0 and 133.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
Component: Internationalization → Site Reports
Product: Core → Web Compatibility
You need to log in before you can comment on or make changes to this bug.