.nr{ --ink:#16181d; --muted:#667085; --muted2:#667085; --line:#dfe5ec; --line2:#c9d6e6; --soft:#f6f8fb; --day-band:#f6f8fb; /* the news feed day band -- the one tinted element inside the card */ --blue:#1668d6; --blue-dark:#1668d6; --blue2:#1668d6; --blue-soft:#eef5ff; --green:#16844a; --green-soft:#edf9f1; --amber:#b66a00; --amber-soft:#fff6e7; --red:#be3d32; --red-soft:#fff0ef; --purple:#6b4fd3; --purple-soft:#f3f0ff; --radius:16px; --shadow:0 8px 28px rgba(17,24,39,.06); /* var(--page-bg) since 2026-08-25. /news was the only page on pure white; every other surface sits on #f8fafc. Its cards are #fff, so on white they were defined by their borders alone and now read as cards the way they do everywhere else. */ background:var(--page-bg); color:var(--ink); font-family:var(--font-inter,"Inter",system-ui,sans-serif); -webkit-font-smoothing:antialiased; } .nr *{box-sizing:border-box} .nr a{text-decoration:none;color:inherit} /* THE THREE CARD SHAPES ARE PASSED IN DELIBERATELY. The anchor wraps the headline TEXT only, and .lead, .mini and .item are each far larger than it -- so hover on the anchor alone would leave most of the card the reader is pointing at inert. See headlineLinkCss in primitives.tsx. */ .nr h3 a{text-decoration:none;transition:text-decoration-color .15s ease} .nr h3 a:hover,.nr h3 a:focus-visible,.nr .lead:hover h3 a,.nr .mini:hover h3 a,.nr .item:hover h3 a{text-decoration:underline; text-decoration-thickness:1px;text-underline-offset:4px; text-decoration-color:var(--id-link-rule, rgba(22, 104, 214, 0.45))} .nr h3 a:focus-visible{outline:2px solid #1668d6;outline-offset:3px} @media (prefers-reduced-motion:reduce){.nr h3 a{transition:none}} /* ── ONE CONTENT WIDTH (Kevin, 2026-09-04) ───────────────────────────────────────────────── "it needs to be same width as any sub nav etc above it". Measured at 1440 across seventeen public pages, the container that holds the page title declared EIGHT widths: 1240 (home, hubs), 1184 (prices), 1180 (roadmaps, devices), 1160 (news), 1140 (about, methodology), 1080 (record), 960 (sources), 860 (scorecard). The GUIDE was the only surface whose sub-nav and body already agreed, and the value they agree on is CONTENT_MAX -- 1120 -- which lib/designStandards.ts has declared all along. So this is not a new number, it is the declared one the densest page already proves. See THE CONTAINER STANDARD in designStandards.ts. */ .nr .wrap{max-width:1120px;margin:0 auto;padding:0 clamp(16px, 2.5vw, 24px)} /* ── Page head (all-news) ─────────────────────────────────────────────── */ .nr .page-head{padding:42px 0 24px} .nr .eyebrow{font-size:var(--fs-3xs);font-weight:600;text-transform:uppercase;letter-spacing:.08em;color:var(--blue)} /* PAGE TITLE TOKENS (Kevin, 2026-09-04). Nine sizes, five weights and eight letter-spacings across sixteen public pages was not sixteen decisions. See THE PAGE TITLE in lib/designStandards.ts for the measurement and for why the token is a clamp. */ .nr h1{font-size:clamp(30px,4.4vw,46px);line-height:1.05;letter-spacing:-0.02em;margin:8px 0 10px;font-weight:800} .nr .lede{font-size:var(--fs-base);line-height:1.55;color:#475467;max-width:720px;margin:0} .nr .searchbar{ margin-top:24px;border:1px solid var(--line2);border-radius:16px;height:50px; display:flex;align-items:center;gap:12px;padding:0 15px;box-shadow:0 1px 0 rgba(16,24,40,.02) } .nr .searchbar .lens{width:17px;height:17px;border:2px solid #667085;border-radius:50%;position:relative;flex:0 0 auto} .nr .searchbar .lens:after{content:"";position:absolute;width:6px;height:2px;background:#667085;right:-5px;bottom:-3px;transform:rotate(45deg)} /* The outline suppression that used to sit in this rule is gone: the searchbar wrapper draws no focus-within treatment, so it left the search field with no focus indicator for a keyboard reader. */ .nr .searchbar input{border:0;width:100%;font:inherit;font-size:var(--fs-sm);color:#475467;background:transparent} .nr .searchbar input:focus-visible{outline:2px solid #1668d6;outline-offset:2px} .nr .searchbar kbd{border:1px solid var(--line);background:#f6f8fb;border-radius:8px;padding:4px 7px;color:#667085;font-size:var(--fs-2xs)} /* ── Filters ──────────────────────────────────────────────────────────── */ .nr .filter-area{border-bottom:1px solid var(--line);padding-bottom:18px} /* ── THE JOINED TRACK, SAME AS /devices (Kevin, 2026-08-28: "I thought we changed away from the segmented pills and black fill") ────────────────────────────────────────────────────────────── /devices was moved off separate chips with a black active pill on 2026-08-28 and this row was not, so the same control looked two ways on the same site — which is the drift the whole sweep exists to end. Two reasons the track wins here as well. The category row runs to eight items and already wrapped or overflowed on a laptop, and one scrolling object can say so with an edge fade where wrapped chips cannot. And the black active pill was the heaviest thing on the page while filtering a list, in a colour that appears nowhere else in this palette. The active state is a raised white tile on a grey track — the settings-screen segmented control — so it reads as "this one" without claiming to be the page's action. (No backticks in this comment: the whole block is a template literal.) */ /* THE TRACK HUGS ITS CHIPS (2026-09-04). Measured on the live /news at 1440: the row was 1104px wide -- the full content column -- while the last chip ended 421px short of it, so a third of the control was empty grey rail. A segmented control that runs past its own last segment reads as a loading state. width:max-content sizes it to the chips; max-width:100% is unchanged, so the moment the chips do not fit the row still scrolls exactly as before. */ .nr .cat-row{--strip:#f2f5f9;--strip-0:rgba(242,245,249,0);position:relative;display:flex; align-items:center;gap:2px;padding:4px;border-radius:999px;background:var(--strip); overflow-x:auto;scrollbar-width:none;width:max-content;max-width:100%} .nr .cat-row::-webkit-scrollbar{display:none} .nr .cat{ flex:0 0 auto;border:1px solid transparent;border-radius:999px;padding:7px 14px;background:transparent; color:#475467;font-size:var(--fs-2xs);font-weight:600;cursor:pointer;white-space:nowrap; transition:background-color .15s ease,color .15s ease,box-shadow .15s ease } .nr .cat.active{background:#ffffff;color:#16181d;border-color:transparent; box-shadow:0 1px 2px rgba(15,23,42,.07),0 3px 8px rgba(35,52,75,.09)} .nr .cat:hover{background:rgba(15,23,42,.05);color:#16181d} .nr .cat.active:hover{background:#ffffff} .nr .cat:focus-visible{outline:2px solid #1668d6;outline-offset:-1px} @media (prefers-reduced-motion:reduce){.nr .cat{transition:none}} .nr .tool-row{ display:flex;justify-content:space-between;align-items:center;gap:14px;margin-top:13px } .nr .tool-left,.nr .tool-right{display:flex;align-items:center;gap:8px;flex-wrap:wrap} .nr .control{ display:inline-flex;align-items:center;gap:7px;padding:8px 11px;border:1px solid var(--line); border-radius:9px;background:#ffffff;color:#5e6877;font-size:var(--fs-3xs);font-weight:600 } .nr button.control{cursor:pointer;font-family:inherit} .nr .control b{color:#2f3744} .nr .unread{color:var(--blue);font-weight:600;font-size:var(--fs-3xs)} .nr .keyboard{font-size:var(--fs-2xs);color:#667085} /* ── Top stories ──────────────────────────────────────────────────────── */ .nr main{padding:28px 0 72px} .nr .section-title{display:flex;align-items:end;justify-content:space-between;gap:20px;margin-bottom:14px} .nr h2{font-size:22px;letter-spacing:-.5px;margin:0;font-weight:600} .nr .section-title p{font-size:var(--fs-3xs);color:#667085;margin:0} .nr .top-grid{display:grid;grid-template-columns:1.45fr .8fr;gap:12px;margin-bottom:36px} /* The lead card carries its image at the top, per the approved news-index artifact. min-height stays for the no-image case so the grid row does not collapse against the two minis beside it, but it is now a floor on a filled card rather than a reservation for nothing. */ .nr .lead-media{ margin:-24px -24px 4px;height:230px;overflow:hidden; border-radius:18px 18px 0 0;background:#e9eff7; } .nr .lead-media img{width:100%;height:100%;object-fit:cover;display:block} @media (max-width:900px){.nr .lead-media{height:180px}} .nr .lead{ min-height:310px;border:1px solid var(--line);border-radius:18px;padding:24px; position:relative;overflow:hidden;background: radial-gradient(circle at 82% 20%,rgba(23,105,255,.15),transparent 34%), linear-gradient(135deg,#f9fbff,#f4f7fb); } .nr .lead:after{ content:"";position:absolute;width:250px;height:250px;border:42px solid rgba(23,105,255,.07); border-radius:50%;right:-66px;bottom:-86px } .nr .lead > *{position:relative;z-index:1} .nr .story-kicker{font-size:var(--fs-3xs);text-transform:uppercase;letter-spacing:.07em;color:var(--blue);font-weight:600} .nr .lead h3{font-size:29px;line-height:1.13;letter-spacing:-1px;margin:10px 0 10px;max-width:650px;font-weight:600} .nr .lead .summary{font-size:var(--fs-xs);color:#5d6676;line-height:1.55;max-width:660px;margin:0} .nr .meta{display:flex;align-items:center;gap:8px;flex-wrap:wrap;color:#667085;font-size:var(--fs-2xs);margin-top:16px} .nr .source-name{font-weight:600;color:#475467} .nr .tag,.nr .type{display:inline-flex;align-items:center;gap:6px;flex-shrink:0;padding:4px 12px;border-radius:999px;font-size:12.5px;line-height:17px;font-weight:600;letter-spacing:0px;text-transform:none;white-space:nowrap;font-family:var(--font-inter, system-ui, sans-serif);border:1px solid} .nr .tag::before,.nr .type::before{content:"";width:12px;height:12px;flex:none;background:currentColor;-webkit-mask:var(--tag-ic) center/contain no-repeat;mask:var(--tag-ic) center/contain no-repeat} .nr .tag.news,.nr .type.news{--tag-ic:url("data:image/svg+xml;utf8,");background:#eeeff1;color:#4c5564;border-color:transparent} .nr .tag.leak,.nr .type.leak{--tag-ic:url("data:image/svg+xml;utf8,");background:#e7eefb;color:#0f4bb7;border-color:transparent} .nr .tag.update,.nr .type.update{--tag-ic:url("data:image/svg+xml;utf8,");background:#e8f3ed;color:#157142;border-color:transparent} .nr .tag.review,.nr .type.review{--tag-ic:url("data:image/svg+xml;utf8,");background:#f0edfb;color:#5b45b3;border-color:transparent} /* patent / cert removed 2026-08-30: storyTag() cannot return either (no column in the feed payload expresses them) and no other call site emits a .tag class. See .nr .type.* below. */ .nr .impact{display:inline-flex;align-items:center;gap:5px;color:var(--blue-dark);font-size:var(--fs-2xs);font-weight:600} .nr .impact:before{content:"\2197";width:16px;height:16px;border-radius:6px;background:var(--blue-soft);display:flex;align-items:center;justify-content:center} .nr .side-top{display:grid;grid-template-rows:1fr 1fr;gap:12px} .nr .mini{ border:1px solid var(--line);border-radius:16px;padding:17px;background:#ffffff; display:flex;flex-direction:column;justify-content:space-between } .nr .mini h3{font-size:var(--fs-md);line-height:1.32;margin:8px 0 8px;font-weight:600} .nr .mini p{font-size:var(--fs-3xs);line-height:1.46;color:#667085;margin:0} .nr .mini .meta{margin-top:12px} /* ── Feed ─────────────────────────────────────────────────────────────── */ .nr .feed-head{display:flex;justify-content:space-between;align-items:center;margin-bottom:4px} .nr .feed-head h2{font-size:21px} .nr .feed-head .count{font-size:var(--fs-3xs);color:#667085} /* NO FRAME AROUND THE FEED (Kevin, 2026-08-30). The top border above the first day separator and the bottom border under the final row were read together as a deliberate frame; they are not. The day separator already carries its own rule (.nr-day:after) and every row carries a bottom border, so the frame added a fifth and sixth line to a list whose whole structure is lines -- and the last one sat directly on .shortcuts with nothing between them. Both go, as one decision: keeping either half would leave an asymmetric edge that reads as a mistake rather than as a frame. */ /* ── THE FEED IS A CARD, AND THE DAY HEADER IS THE ONLY TINTED THING IN IT (2026-09-02) ─────── Kevin: "expectations, news, all both have zebra white cells on grey ... for news it should probably be in a container with white bg / colored day headers." The stripe was never a stripe rule. Rows carry no background at all, so they showed the page's #f8fafc through, while .nr-day was painted #fff so it could stick without rows scrolling under it -- one white band per day against grey rows, which reads as zebra and is really a sticky-header artifact. So the CARD carries the white, the rows inherit it, and the day header becomes the one tinted element rather than the one white one -- the inverse of what it was doing. (No backticks anywhere in this comment: the whole block is one template literal, and putting one around a class name here is the defect CLAUDE.md has recorded eleven times.) */ .nr .feed{ border-top:0;background:#ffffff;border:1px solid var(--line);border-radius:var(--radius); padding:0 22px 4px;box-shadow:var(--shadow) } /* :last-of-type, NOT :last-child -- the feed ends with a sentinel DIV (infinite-scroll trigger), so the last row is never its parent last child. Rows are

and the day separators are

, so last-of-type names exactly the final row and keeps naming it as more pages load. */ .nr .feed article:last-of-type{border-bottom:0} /* DAY SEPARATOR (2026-08-24). Sticky under the site header so the reader always knows which day the rows on screen belong to while scrolling a feed that runs weeks deep. Sits above .item's bottom border rather than carrying its own, so two rules never draw two lines. */ .nr .nr-day{ /* Sticks BELOW the site nav, not under it. nav.site-nav is a fixed 72px bar that becomes 58px somewhere between 1024 and 900 -- measured, because guessing the offset is how a sticky heading ends up invisible behind a header while every DOM assertion still passes. */ position:sticky;top:72px;z-index:3; /* Full-bleed across the card's 22px padding so the tint reaches both edges and reads as a band rather than a floating chip. NOT var(--strip): that token is declared on .cat-row, so it does not inherit here and would silently fall back. */ background:var(--day-band);margin:0 -22px;padding:11px 22px; /* ── NO BORDERS ON THE BAND (2026-09-02, same day it grew them) ───────────────────────── Kevin: "there is a line below the last cell that should not be there (above the grey header bar)". Every .nr .item already draws a border-bottom, and the band sits directly against it at a ZERO gap -- measured in the browser: 1px row border, 1px band border, 0px between them, so the boundary rendered as a doubled 2px rule. The tint IS the boundary; a band that changes colour does not also need a line to say it started. The border-bottom I added alongside it was dead on arrival anyway -- border-bottom:0 still sits at the end of this same rule and overrode it, which the computed style confirmed at 0px. Removing both rather than leaving one that does nothing. The first-child rule below keeps its border-top:0 for the same reason it always had it. */ display:flex;align-items:center;gap:11px; font-size:var(--fs-3xs);font-weight:600;letter-spacing:.08em;text-transform:uppercase; color:#667085;border-bottom:0 } /* THE SEPARATOR IS A RULE, NOT A BAR. It was a full-width band with a bottom border, which gave a divider the same visual weight as the stories it divides — and on a feed the stories are the content. The rule runs to the right of the label so the eye reads the word and then travels along it into the first row, rather than stopping at an edge. (No backticks in this comment: the whole block is a template literal.) */ /* The trailing rule existed to carry the eye off a white LABEL into the first row. A tinted band already spans the width, so a second horizontal line inside it is one line too many. */ .nr .nr-day{color:#5b6473} /* The first band sits directly under the card top border; a second line there reads as a doubled edge. Its corners follow the card radius so the tint never squares off the rounding. */ .nr .feed .nr-day:first-child{border-top:0;border-radius:var(--radius) var(--radius) 0 0;margin-top:0} .nr .item{ /* ── 76px, NOT 62 (Kevin, 2026-09-20: "accessories is too long") ────────────────────────── He is right about the word and the column is the other half. 62px was sized for a CLOCK ("9:41 AM") and this morning the story tag moved in beside it, so a column built for one thing now holds two. Measured on the live feed: Apps 50, News 54, Rumor 62, Review 65, Update 66, Accessories 103 — so Review and Update were already a few pixels over and nobody had noticed, because only the longest word makes an overflow visible. 76 clears every tag in the vocabulary with room, and the tag is the widest thing here now. Shortening one word without widening the column would have left the same bug waiting behind the next-longest one. */ display:grid;grid-template-columns:76px 1fr 106px;gap:18px;padding:20px 0; border-bottom:1px solid var(--line);position:relative } /* The date column holds the freshness stamp and the outline tag, stacked (2026-09-20). It was a bare clock; the tag came here from the headline row so the two read as one unit. */ .nr .time{display:flex;flex-direction:column;align-items:flex-start;gap:7px; font-size:var(--fs-3xs);color:#667085;padding-top:4px} .nr .time b{display:block;color:#475467;font-size:var(--fs-2xs);margin:0;font-weight:600} .nr .item-main{min-width:0} .nr .item-top{display:flex;align-items:center;gap:8px;flex-wrap:wrap} .nr .product{ font-size:var(--fs-3xs);color:var(--blue);font-weight:600;text-transform:uppercase;letter-spacing:.065em } .nr .item h3{font-size:var(--fs-base);line-height:1.32;margin:6px 0 6px;letter-spacing:-.2px;font-weight:600} .nr .item p{font-size:var(--fs-2xs);line-height:1.5;color:#667085;margin:0;max-width:770px} .nr .item-bottom{display:flex;align-items:center;gap:10px;flex-wrap:wrap;margin-top:10px} .nr .cluster{ display:inline-flex;align-items:center;gap:6px;font-size:var(--fs-2xs);font-weight:600;color:#445065 } .nr button.cluster{border:0;background:none;padding:0;cursor:pointer;font-family:inherit} .nr .dots{display:flex} .nr .dots i{width:18px;height:18px;border:2px solid #ffffff;border-radius:50%;background:#d6dce5;margin-left:-5px} .nr .dots i:first-child{margin-left:0;background:#b8c8e3} .nr .dots i:nth-child(2){background:#d1d7e1} .nr .dots i:nth-child(3){background:#93a7c7} .nr .updated{font-size:var(--fs-2xs);color:#667085} .nr .thumb{ width:106px;height:74px;border:1px solid var(--line);border-radius:12px;overflow:hidden; display:flex;align-items:center;justify-content:center;position:relative } .nr .thumb span{font-size:var(--fs-3xs);color:#7c8796;text-transform:uppercase;letter-spacing:.06em;font-weight:600} .nr .thumb img{position:absolute;inset:0;width:100%;height:100%;object-fit:cover} .nr .thumb.phone{background:linear-gradient(145deg,#e9effa,#f8fafc)} .nr .thumb.watch{background:linear-gradient(145deg,#eaf6ef,#f8fafc)} .nr .thumb.glasses{background:linear-gradient(145deg,#f1eefc,#f8fafc)} .nr .thumb.ear{background:linear-gradient(145deg,#fff3e6,#f8fafc)} .nr .thumb.ring{background:linear-gradient(145deg,#eef4f5,#f8fafc)} .nr .thumb.xr{background:linear-gradient(145deg,#edf3ff,#f5f7fa)} .nr .item.unseen:before{ content:"";position:absolute;left:-15px;top:27px;width:6px;height:6px;border-radius:50%;background:var(--blue) } .nr .item.seen{opacity:.5} /* ── Cluster expansion ────────────────────────────────────────────────── */ .nr .cluster-card{ margin:7px 0 22px 78px;border:1px solid #d9e4f7;border-radius:16px;background:#fbfdff;padding:14px 16px } .nr .cluster-title{display:flex;justify-content:space-between;gap:12px;align-items:center} .nr .cluster-title b{font-size:var(--fs-2xs)} .nr .cluster-title span{font-size:var(--fs-2xs);color:#8490a0} .nr .sources{display:grid;grid-template-columns:repeat(3,1fr);gap:8px;margin-top:11px} .nr .source-card{border:1px solid var(--line);border-radius:9px;padding:10px;background:#ffffff} .nr .source-card b{display:block;font-size:var(--fs-3xs)} .nr .source-card span{font-size:var(--fs-2xs);color:#667085} /* ── Shortcuts bar ────────────────────────────────────────────────────── */ .nr .shortcuts{ display:flex;justify-content:space-between;gap:20px;align-items:center; margin-top:18px;padding:12px 14px;border-radius:12px;background:#f6f8fb;color:#667085;font-size:var(--fs-2xs) } .nr .shortcuts kbd{border:1px solid #dce1e8;border-bottom-width:2px;background:white;border-radius:6px;padding:2px 5px;color:#475467} /* A keyboard-shortcut bar on a device with no keyboard is a row of instructions the reader cannot follow. Hidden by POINTER TYPE rather than by width: a 900px-wide tablet has no keys and a narrow desktop window does, and only a pointer:coarse query can tell those apart. Nothing SEO-critical is inside it — it is an affordance, not content — so hiding it is not a Rule 5 problem. */ @media (pointer: coarse){ .nr .shortcuts{display:none} } /* ══ PRODUCT-SCOPED VIEW ═══════════════════════════════════════════════ Ported from efd44c9b-ideviceproductnewstrackerappleglasses.html. Its :root redeclares --line as #e6eaf0 and --line2 as #d8dee8 (one hex step from the all-news mockup); .nr-product carries that so both remain verbatim. */ .nr.nr-product{--line:#dfe5ec;--line2:#c9d6e6;--muted:#667085;--muted2:#667085} .nr .product-context{ margin-top:20px;border:1px solid var(--line);border-radius:18px;background:#ffffff;overflow:hidden; } .nr .product-main{ display:grid;grid-template-columns:1fr auto;gap:20px;align-items:center;padding:18px 20px 16px; } .nr .product-kicker{ display:flex;align-items:center;gap:8px;font-size:var(--fs-3xs);text-transform:uppercase;letter-spacing:.07em;font-weight:600;color:var(--blue); } .nr .product-kicker:before{content:"";width:7px;height:7px;border-radius:50%;background:var(--blue)} .nr .product-main h2{font-size:26px;letter-spacing:-.8px;margin:6px 0 5px} .nr .product-main p{font-size:var(--fs-2xs);color:#667085;line-height:1.5;margin:0;max-width:690px} .nr .product-status{text-align:right} .nr .product-status b{display:block;font-size:var(--fs-xs)} .nr .product-status span{display:block;font-size:var(--fs-2xs);color:#667085;margin-top:3px} .nr .product-tabs{ display:grid;grid-template-columns:1fr 1fr;border-top:1px solid var(--line);background:#fcfcfd; } .nr .product-tabs a{ padding:12px 18px;border-left:1px solid var(--line);font-size:var(--fs-3xs);font-weight:600; } .nr .product-tabs a:first-child{border-left:0} .nr .product-tabs a.active{background:#f8fbff;color:var(--blue)} .nr .product-tabs small{display:block;margin-top:4px;font-size:var(--fs-2xs);font-weight:600;color:#7e8795} .nr .product-tabs a.active small{color:var(--blue)} .nr .feed-header{ display:flex;justify-content:space-between;align-items:end;gap:20px;margin-top:28px;margin-bottom:10px; } .nr .feed-header h2{margin:0;font-size:var(--fs-xl);letter-spacing:-.5px} .nr .feed-header p{margin:4px 0 0;font-size:var(--fs-3xs);color:#667085} .nr .story{ display:grid;grid-template-columns:82px 1fr 110px;gap:18px;padding:20px 0;border-bottom:1px solid var(--line); position:relative; } .nr .story .time{font-size:var(--fs-2xs);color:#667085;line-height:1.4;padding-top:2px} .nr .story .time b{display:block;font-size:var(--fs-3xs);color:#5d6674;margin:0} .nr .story-main{min-width:0} .nr .story-top{display:flex;gap:7px;align-items:center;flex-wrap:wrap} /* .nr .type is declared WITH .nr .tag above -- one badge, two layouts. */ /* THE STORY VARIANT'S PILL CLASSES MUST BE THE ONES storyTag() EMITS (2026-08-30). Two badge trees were authored independently -- .tag.* for variant="item" and .type.* for variant="story" -- and only one of them was keyed on the class names the shared producer actually returns. storyTag() (components/news/newsFormat.ts) returns cls in {news, leak, review, update} and nothing else, so on /news?brand= every pill fell through to the base grey while the identical categories rendered in colour on /news. The four values below are the WHOLE range of that function. The previous three (patent / report / official) were emitted by nothing anywhere in the frontend -- confirmed by grepping every className construction and every cls: return -- and are removed rather than left as a fourth vocabulary for a future reader to reconcile. Colours are the .tag.* values verbatim, because the two variants are the same badge on two layouts and a second palette is how they drifted in the first place. */ /* Colours for both variants are generated from STORY_TOKENS above. */ .nr .story h3{font-size:var(--fs-base);line-height:1.33;letter-spacing:-.2px;margin:7px 0 6px;font-weight:600} .nr .story p{font-size:var(--fs-2xs);line-height:1.5;color:#667085;margin:0;max-width:770px} .nr .story-meta{display:flex;gap:9px;align-items:center;flex-wrap:wrap;margin-top:10px;font-size:var(--fs-2xs);color:#667085} .nr .story-meta b{color:#475467} .nr .story .thumb{ width:110px;height:76px;border:1px solid var(--line);border-radius:12px; background:linear-gradient(145deg,#f0f4fa,#fbfcfd); position:relative;overflow:hidden; } .nr .story .cluster-card{margin-left:82px} .nr .related{margin:34px 0 56px;border-top:1px solid var(--line);padding-top:20px} .nr .related-head{display:flex;justify-content:space-between;align-items:center;margin-bottom:10px} .nr .related h2{font-size:var(--fs-lg);margin:0} .nr .related-head span{font-size:var(--fs-2xs);color:#667085} .nr .products{display:flex;gap:8px;flex-wrap:wrap} .nr .product-pill{ border:1px solid var(--line);border-radius:999px;padding:8px 11px;font-size:var(--fs-2xs);font-weight:600;color:#475467;background:#ffffff; } .nr .product-pill.active{background:var(--blue-soft);border-color:#c8dcff;color:var(--blue2)} /* ── Loading / empty ──────────────────────────────────────────────────── */ .nr .nr-skel{border-bottom:1px solid var(--line);padding:20px 0;display:grid;grid-template-columns:78px 1fr 106px;gap:18px} .nr .nr-skel i{display:block;background:linear-gradient(90deg,rgba(16,19,26,.05) 25%,rgba(16,19,26,.02) 50%,rgba(16,19,26,.05) 75%);background-size:400px 100%;animation:nr-shimmer 1.4s infinite linear;border-radius:4px} @keyframes nr-shimmer{0%{background-position:-200px 0}100%{background-position:200px 0}} .nr .nr-empty{padding:44px 0;text-align:center;color:#667085;font-size:var(--fs-xs)} .nr .nr-end{padding:20px 0;text-align:center;color:#667085;font-size:var(--fs-3xs)} /* ── Mobile ───────────────────────────────────────────────────────────── */ @media(max-width:1023px){ .nr .nr-day{top:58px} } @media(max-width:820px){ .nr .wrap{padding:0 18px} .nr .top-grid{grid-template-columns:1fr} .nr .side-top{grid-template-columns:1fr 1fr;grid-template-rows:auto} .nr .item{grid-template-columns:1fr 84px;gap:12px} .nr .item .time{grid-column:1/-1;padding:0} .nr .thumb{width:84px;height:64px} .nr .cluster-card{margin-left:0} .nr .sources{grid-template-columns:1fr} .nr .product-main{grid-template-columns:1fr} .nr .product-status{text-align:left} .nr .story{grid-template-columns:1fr 82px} .nr .story .time{grid-column:1/-1} .nr .story .thumb{width:82px;height:64px} .nr .story .cluster-card{margin-left:0} } @media(max-width:560px){ .nr .side-top{grid-template-columns:1fr} .nr .tool-row{align-items:flex-start;flex-direction:column} .nr .item{grid-template-columns:1fr} .nr .item .thumb{display:none} .nr .nr-skel{grid-template-columns:1fr} }

Pixel news

The Pixel 10a now costs $599 after a $100 price hike from Google

The Pixel 11a leaks with the Tensor G6 that the Pixel 10a never got

The Pixel 11a leaks with the Tensor G6 that the Pixel 10a never got