Description of the Bug
The series age-rating filter description says that only series rated N or lower will be shown. However, SeriesFilterForm converts the selected value into metadata.ageRating.gte, meaning N or higher. Its default-value mapping also reads gte.
For an input of 12:
- The description promises an upper bound:
ageRating <= 12.
- The form constructs a lower bound:
ageRating >= 12.
A series explicitly rated 16 therefore falls on opposite sides of the described and constructed filters. This report concerns the browsing filter, not account-level age restrictions or an authorization bypass.
Expected Behavior
The description and the submitted filter should use the same comparison direction. Could you clarify whether this control is intended to set a minimum or a maximum age rating?
If gte is intended, the series description should say “N or higher”. If the description is intended, the form's submission and default-value mapping should use the corresponding upper-bound operator. A regression case with ratings below, equal to, and above the selected value would help keep these aligned.
Steps To Reproduce
This report is based on source inspection; the following UI reproduction is proposed and has not been run against a server:
- Use series with explicit age ratings of 8, 12, and 16, with no other filters or account-level age restrictions affecting the result.
- Open the series browsing filter and enter 12 in the custom age-rating control.
- Read the description, then apply the filter and inspect the GraphQL variables.
- Check whether the filter contains
metadata.ageRating.gte: 12, as constructed by the form, rather than lte: 12 as the description implies.
Where is this issue happening?
Server & Client Details
Inspected nightly commit c784afeae314a293c5ff4a525513a7a0f98c84d5. This is a source-based report, not a claim of reproduction on a deployed release; runtime OS, Docker, and browser details are not applicable.
Additional context
Found while reviewing the Korean translation. The series description was left pending because translating it literally would preserve the mismatch.
Description of the Bug
The series age-rating filter description says that only series rated N or lower will be shown. However,
SeriesFilterFormconverts the selected value intometadata.ageRating.gte, meaning N or higher. Its default-value mapping also readsgte.For an input of 12:
ageRating <= 12.ageRating >= 12.A series explicitly rated 16 therefore falls on opposite sides of the described and constructed filters. This report concerns the browsing filter, not account-level age restrictions or an authorization bypass.
Expected Behavior
The description and the submitted filter should use the same comparison direction. Could you clarify whether this control is intended to set a minimum or a maximum age rating?
If
gteis intended, the series description should say “N or higher”. If the description is intended, the form's submission and default-value mapping should use the corresponding upper-bound operator. A regression case with ratings below, equal to, and above the selected value would help keep these aligned.Steps To Reproduce
This report is based on source inspection; the following UI reproduction is proposed and has not been run against a server:
metadata.ageRating.gte: 12, as constructed by the form, rather thanlte: 12as the description implies.Where is this issue happening?
Server & Client Details
Inspected
nightlycommitc784afeae314a293c5ff4a525513a7a0f98c84d5. This is a source-based report, not a claim of reproduction on a deployed release; runtime OS, Docker, and browser details are not applicable.Additional context
Found while reviewing the Korean translation. The series description was left pending because translating it literally would preserve the mismatch.