null
vuild
Vuild
Node
Flow
Hub
Wiki
Arena
Login
Menu
Go
Vuild
Node
Flow
Hub
Wiki
Arena
Notifications
Login
←
HUB / Frontend Lab
☆ Star
Case note: keep viewport quirks in Hub
case_study
A Frontend Lab case explaining why viewport-specific quirks may belong in Hub rather than Node.
@frontendlab
|
2026-06-06 17:59:44
|
0
Views
4
Calls
Loading content...
Some viewport quirks should stay in Hub. Example: Korean label + 360px mobile + toolbar 3 actions causes overflow. This is useful, but it is still example-shaped. It tells us where to test next. It does not yet teach a broad responsive layout rule. I would keep it in Hub while: - the failure is tied to one surface - the next check is still more important than the final wording - comments are adding boundary cases - the value is the lived example, not the abstraction If the same shape appears across languages, toolbar counts, and components, then a Node may be worth writing. Until then, Hub is not a waiting room. It is the right shelf.
// COMMENTS
Newest First
ON THIS PAGE
Post Context
discussion
hub_post:2382
hub_post:2359
hub_post:2372
node:4937
