Bookmark sites share the tab favicon renderer: saved image, then the site origin’s /favicon.ico, then the Lucide browser fallback. Only HTTP(S) and image data sources are accepted; requests omit referrers and never use a third-party favicon service. New bookmarks retain the current page icon, and revisiting an exact bookmarked URL refreshes its saved icon without erasing it on empty loading state. The bar keeps its existing height and shows bar items, a double-chevron hidden-items menu, a divider, and All bookmarks at the right. All bookmarks opens the existing manager, which retains Other bookmarks and Mobile bookmarks in their original hierarchy. Folder icons remain folders. Acceptance requires actual imported leaves, failed image fallback, icon replacement, overflow actions and manager access. Reference: Chrome bookmark help and the supplied Chrome screenshots.

During native page loading, the Reload control becomes an accented Lucide X with the accessible name Stop loading. A thin indeterminate progress indicator appears below the browser toolbar, without changing its height. Stop cancels loading; completion, failure, and cancellation remove the indicator and restore Reload. The indicator reflects native loading events, does not invent a percentage, and stays static under reduced-motion preferences.

When a webpage prevents reload or navigation with beforeunload, its current owning window displays a native confirmation. Stay on page is the default and cancel action; Leave page permits only the blocked operation. Missing ownership, destruction, or dialog failure keeps the page. Ordinary reloads need no confirmation. This uses Electron's will-prevent-unload event; tab-close and application-shutdown policy are outside this change.

Ordinary tabs and split members use the site favicon when it decodes to visible pixels, with the existing animated Lucide browser icon while loading or on failure. The desktop process reads favicon bytes through the page session, limits requests to HTTP(S) and image data, bounds downloads to 256 KiB and five seconds, and sends image data URLs so the renderer can detect fully transparent icons. Navigation and destruction cancel pending reads; stale results cannot replace the current page icon. State snapshots include the current favicon when a retained page is reopened. Browsing history keeps the original site icon URL.

An empty pane only shows Files, New chat, Browser, and Terminal. The address bar, quick sites, Bookmarks, and History do not appear here.

Files, New chat, Browser, and Terminal all use equally sized rounded icon containers and Lucide outline icons. Files uses blue, New chat green, Browser orange and purple, and Terminal purple. Color only identifies content types; it does not change card hierarchy, interaction states, or accessible names, and introduces no brand logos, external assets, or extra animation.

Selecting Browser opens browser home in place. Home and actual pages share the address bar and bookmarks bar structure. Back, Forward, Reload, Home, Bookmark, and external opening remain visible but disabled when no current page applies; address input, Bookmarks, Import, and Browser ⋯ remain available.

Ordinary links, form submissions, script assignments, and same-document navigation continue to commit in the current WebContentsView and only update that WebTab's URL, title, and History; they must not create a tab. Only when the page explicitly requests a new browsing context (target="_blank" or window.open) does the main process convert a validated HTTP(S) URL into a WebTab with its own id. The new WebTab immediately becomes active; when already at /chat or /s/<id> , do not push /chatagain, so session-route synchronization cannot overwrite popup activation.

The native page area directly uses Electron context-menu hit parameters. HTTP(S) links show Open Link in New Tab and Copy Link Address; editable content shows Undo, Redo, Cut, Copy, Paste, and Select All; ordinary pages show Back, Forward, and Reload. Open Link in New Tab reuses the popup entry point and therefore has the same semantics as the page's own window.open for URL validation, unique tabs, and immediate activation. Menu actions only affect the WebTab that produced the menu and is still owned by the same window.

A floating web preview opened by an agent in chat records its session tab at creation. It appears only while that session is the current center content. Switching to another chat, a regular Browser tab, or a non-chat page must remove the WebTab from the renderer's native visible set and restore the user's web zoom. Returning to the original session reuses the same WebTab, URL, scroll position, and form state without reloading. After the user closes the preview, its restore entry also appears only in that session.

The star at the right of the address bar only saves or removes the current page; the adjacent Bookmarks button opens the complete bookmarks page. Browser home shows only user-maintained quick sites, not all bookmarks.

The complete bookmarks page has a fixed page title, search field, and page menu at the top. The left column contains only a collapsible folder tree with the current directory highlighted; the right column contains only that directory's direct children. Bookmark rows have a favicon, title, and single ⋮ menu; folder rows open the corresponding directory. The entire tree, URLs, and edit/delete buttons no longer share one list. Rows in both lists use 36px; the search field uses the global 30px control height, inline icon buttons use 28px, and the header uses 52px. The right list's initial viewport padding is 16px. In a narrow pane, the directory tree moves above the content list rather than disappearing.

Browser home and actual pages show the same bookmarks row below the address bar by default. Users can disable it through Browser ⋯ or Settings. Narrow split panes temporarily hide the row, while all content remains accessible through Bookmarks in Browser ⋯ .

Chromium's Bookmarks bar is the bookmarks-bar container, not an ordinary folder button. Its direct children enter the bar in original order;Other bookmarks and Mobile bookmarks remain in the manager, reached through All bookmarks after the overflow control and divider. Ordinary root bookmarks remain bar items. Items placed in overflow must not leave partially clipped buttons in the visible bar; the last visible button must retain its full background and both rounded ends.

The single-row bookmarks bar has no horizontal scrollbar; items that exceed its width appear in the right-side overflow menu. Menus have a fixed width of 280px and ellipsize long titles. Folder rows show a Folder icon in the existing 14px icon slot and a right arrow to enter the next menu, rather than concatenating full paths. Site rows show bookmark favicons; when imported data lacks a favicon, fetch it from the URL and show a Bookmark icon on failure, never an empty slot. In the desktop App, hovering over a bookmarks-bar folder opens it immediately, and moving horizontally to an adjacent folder switches menus without extra delay. Consecutive folder switches reuse one menu view and replace only its data, without rebuilding the view or decoding previously displayed favicons again. The native overlay starts at the bookmarks bar's lower edge and must not cover the buttons' pointer hit areas. Each menu level is constrained by the current window height and supports mouse, trackpad, and keyboard interaction.

Settings in the window menu opens OpenProgram settings; Browser's ⋯ opens its Browser section directly. The toolbar adds no persistent gear button and no second browser-settings store.

Splitting, leaving split view, and pane arrangement apply to Files, Chat, Browser, and Terminal; they are not current-page actions. They belong in Tab/Pane controls or the tab context menu, not the browser toolbar.

Chromium's bookmark bar, other bookmarks, and nested folders retain their hierarchy and order in the OpenProgram bookmark tree. Import must not flatten bookmarks into separate entries below home.

Browser ⋯ and the window ⋯ use their respective trigger buttons' actual screen rectangles. The menu's right edge aligns with the button's right edge, with a 4px vertical gap; the two menus cannot share placement or content.

Records are grouped by local date. Each row shows only time, favicon, title, domain, and actions; the full URL no longer occupies a second line.

The source browser, profile, and data types are confirmed separately. OpenProgram does not read or modify the source profile actively used by the user.