Closed Bug 2003813 Opened 2 months ago Closed 17 days ago

[nsfw] android: CSS seems not applied on adult.contents.fc2.com

Categories

(Web Compatibility :: Site Reports, defect, P2)

Product:
Web Compatibility
Component:
Site Reports
Version:
Firefox 147
Platform:
Unspecified
Android
Type:
defect

Tracking

(Webcompat Priority:P2, Webcompat Score:5)

Status:
RESOLVED FIXED
Project Flags:
Webcompat Priority P2
Webcompat Score 5

People

(Reporter: canalun, Unassigned)

References

(
URL
)

Details

(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat:japan])

User Story

platform:android
impact:significant-visual
configuration:general
affects:all
branch:release
diagnosis-team:layout
user-impact-score:200

Environment
147.0a1 (Build #2016129823), 9336a9aece4
GV: 147.0a1-20251203092053
AS: 147.20251202050421
OS: Android 16

STR
Open https://adult.contents.fc2.com/article/4806136/?dref=index_120234
(NSFW)

AR
The layout is broken.

ER
The layout is not broken. On Chrome, it's not.

URL: https://adult.contents.fc2.com/articl...
OS: Unspecified → Android
Version: unspecified → Firefox 147
Summary: [nsfw] broken layout on adult.contents.fc2.com → [nsfw] android: broken layout on adult.contents.fc2.com

"Layout is broken" isn't really what we can base a good triage on, and it seems like the site needs an account. Can you describe it in a bit more detail? Is the site still usable or completely broken?

Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Flags: needinfo?(i.am.kanaru.sato)
Keywords: webcompat:needs-diagnosis, webcompat:needs-login, webcompat:site-report
Priority: -- → P2

It seems that CSS is not applied almost at all. Usable, but a bit too awkward to use.
It doesn't need any account just to reproduce it. A dialog for age check sometimes appears, but you can just close it.

Flags: needinfo?(i.am.kanaru.sato)
Summary: [nsfw] android: broken layout on adult.contents.fc2.com → [nsfw] android: CSS seems not applied on adult.contents.fc2.com
Whiteboard: [webcompat:japan]
Webcompat Score: 6 → 5
The hash contained in the integrity attribute could not be decoded. 4806136
None of the “sha384” hashes in the integrity attribute match the content of the subresource at “https://static.fc2.com/contents/css/u/article/sp/x793TLu6c82PK-p6ZdvO-h5dNOPZl53_fC7G7K7U.css”. The computed hash is “D1YDjB15SRxJumUo++QWTGS0MaLXFA/of6XGTawbGytJklRv+Xktp2XGTN9ciTWs”.

<link rel="stylesheet" type="text/css" href="//static.fc2.com/contents/css/u/article/sp/x793TLu6c82PK-p6ZdvO-h5dNOPZl53_fC7G7K7U.css" integrity="sha384-contents_source/css/u/article/sp/x793TLu6c82PK-p6ZdvO-h5dNOPZl53_fC7G7K7U.css" crossorigin="anonymous">

My guess is that Chrome is being more lenient in enforcing integrity for valid integrity values.

Randal, who would know whether we or Chrome are doing the right thing here?

Flags: needinfo?(rjesup)

(I'm able to reproduce this in RDM)

Flags: needinfo?(rjesup)

Appears to be fixed for me by bug 2004710

Status: NEW → RESOLVED
Closed: 17 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.