Cobalt – a stripped down Chromium for apps, Linux and embedded systems

Post by pier25 » Wed, Nov 23, 2022, 1:35 AM UTC

devwastaken wrote: post #14

pier25 wrote: post #12

I wonder how this compares to something like Ultralight. https://ultralig.ht/

Ultralight has proprietary components you cannot statically link to.

Post by hdhdxkfchsk » Wed, Nov 23, 2022, 1:57 AM UTC

unwiredben wrote: post #15

Cobalt is the primary engine that's used for running YouTube and YouTube TV on set-top boxes and smart TVs. If you notice that it looks the same on a Roku device or a Fire TV stick or a Samsung TV, that's because all of those are running a port of Cobalt and a special version of the YouTube website.

Post by c-smile » Wed, Nov 23, 2022, 2:16 AM UTC

The_Colonel wrote: post #34

c-smile wrote: post #32

Earlier quoted context omitted.

Sciter supports flex units but not flexbox. Flex units (and grid layouts) are in Sciter since 2007, ~10 years before browsers got them. Flexibility is the must for desktop UIs so it was in the engine from the very beginning. Sciter's flex units + CSS flow property is a superset of flexbox and grid features. For example paddings, margins, border widths, left|right|top|bottom can be expressed in flex units. Everything…

Sciter does not support CSS Flexbox. It supports a more or less equivalent, but incompatible feature. That's a critical distinction when you want to run the same codebase as you have on the web.

   /* browser */
   @supports (display:flex)  
   {
     section { display: flex; }
     section > * { flex: 1; margin:1em; } 
     ...  
   }

   /* sciter */
   @supports (flow:horizontal)
   {
     section { flow:horizontal; }
     section > * { width:1*; margin:1em; }
     ...
   }

Post by GenerocUsername » Wed, Nov 23, 2022, 4:20 AM UTC

anaisbetts wrote: post #25

xcdzvyn wrote: post #23

Earlier quoted context omitted.

> The Cobalt Authors forked H5VCC, removed most of the Chromium code -- in particular WebCore and the Chrome Renderer and Compositor -- and built up from scratch an implementation of a simplified subset of HTML, the CSS Box Model for layout, and the Web APIs that were really needed to build a full-screen SPA browse and play application. So it's based on Chromium, but pretty far from it at this point.

"Based on Chromium" implies that the core rendering code that comprises Chromium is in this codebase, but this is not at all the case if you browse the source. Basically the only thing that this codebase shares with Chromium is a build system and some very low-level libraries (libbase, which is basically a standard library for C++)

Post by Animats » Wed, Nov 23, 2022, 5:10 AM UTC

kaveet wrote: post #35

sandGorgon wrote: post #29

Earlier quoted context omitted.

strange question...but if you were to create a new mobile browser for android (with some custom features), would you recommend Chromium or Cobalt ?

Cobalt isn't a great fit for general-purpose web browsing because it only supports a subset of HTML--lots of websites would appear broken. It's really meant for webapps you've designed with Cobalt in mind. Check out the supported features: https://cobalt.dev/development/reference/supported-features....