Old Chrome Bookmarks Button

ekpljhcfemidkjkebckfdckefbfefbkf

Restores Chrome 63's classic Add to Bookmarks popup with folder memory Attempt to perfectly replicate the "Add to Bookmarks" popup last found in Chrome 63. The original was a native macOS Cocoa UI, not web-rendered. ### `chrome/app/nibs/BookmarkBubble.xib` Interface Builder layout for the main popup (clicking the star icon). - Window: 374 × 145 px - Font (title "Bookmark"): 13pt — `metaFont="system"` - Font (all other controls): 11pt — `metaFont="smallSystem"` - Name input: height 19px, `borderStyle="bezel"`, `controlSize="small"` - Folder picker: height 22px, `NSPopUpButton`, `bezelStyle="rounded"`, `controlSize="small"` - Buttons (Remove, Edit..., Done): height 28px, `bezelStyle="rounded"`, `controlSize="small"` - Done button: `keyEquivalent=" "` — this is what makes macOS color it blue ### `chrome/app/nibs/BookmarkEditor.xib` Interface Builder layout for the Edit Bookmark sheet. - Window: 480 × 270 px - Font (all controls): 13pt — `metaFont="system"` - Name / URL inputs: height 22px, `borderStyle="bezel"` - Folder tree: `NSOutlineView` in `NSScrollView`, height 139px, indent 16px per level - Buttons (New folder, Cancel, Save): height 32px, `bezelStyle="rounded"` - Save button: `keyEquivalent=" "` — colored blue by macOS ### `chrome/browser/ui/cocoa/info_bubble_view.h` Drawing constants for the popup bubble container. - Corner radius: 2px — `kBubbleCornerRadius = 2.0` - Arrow height: 8px — `kBubbleArrowHeight = 8.0` - Arrow width: 15px — `kBubbleArrowWidth = 15.0` - Background: pure white — `[NSColor whiteColor]` ### `chrome/browser/ui/cocoa/bookmarks/bookmark_bubble_controller.mm` Confirmed: folder selector is `NSPopUpButton`, "Choose Another Folder…" at the bottom opens the editor sheet. There are no image assets (PNG, shader, etc.) for any of these controls. Everything — button gradients, glow, the blue NSPopUpButton indicator — is rendered at runtime by macOS AppKit. The CSS in this extension is a manual simulation. Macs with Retina displays use the **Display P3** color space. This causes a mismatch when trying to match CSS colors to a reference screenshot: 1. You write a hex color (e.g. `#2165f6`) in CSS → Chrome treats it as **sRGB** 2. macOS converts sRGB → P3 for display on screen 3. You take a screenshot → macOS saves it tagged with the **Display P3 ICC profile** 4. You open in Photoshop → it reads P3-encoded pixel values → shows a different hex (e.g. `#3d74ed`) Reference screenshots are already in P3. Pixel-sample them directly (e.g. with Python PIL), then feed those values back into CSS as P3 — bypassing the double-conversion: This way the chain is consistent end-to-end: reference screenshot (P3) → CSS P3 values → Chrome renders P3 → screenshot matches reference pixel-for-pixel.

Related extensions