**** BEGIN LOGGING AT Mon Oct 17 02:59:57 2022
Oct 17 08:04:11 <Tofe> Morning!
Oct 17 09:28:25 <JaMa> morning
Oct 17 10:07:20 <Herrie> Morning!
Oct 17 10:07:24 <Herrie> Tofe: That seems to come from https://github.com/webosose/wam/blob/13faf6c1f5249dd3f6159df6b329a30f321c2f38/src/core/web_app_manager.cc#L600-L611
Oct 17 10:07:35 <Herrie> Seems that the "headless" apps in OSE use "system_ui" as well
Oct 17 10:08:51 <Tofe> Yes, and this kWtSystemUi value is passed on as a window property to webruntime, but then I don't see where this is used in webruntime to do any specialization
Oct 17 10:09:13 <Herrie> I.e. https://github.com/webosose/com.webos.app.volume/blob/a8eab274f9cabbf37277d33866020e86d63c877d/webos-meta/appinfo.json#L20, https://github.com/webosose/com.webos.app.home/blob/30bb32dfefc6b4b7ba24d12c63ebcba4d6d161fd/webos-meta/appinfo.json#L11 and https://github.com/webosose/com.webos.app.notification/blob/master/webos-meta/appinfo.json#L12
Oct 17 10:10:16 <Herrie> Well some is here: https://github.com/webosose/wam/blob/31924dad273542ba6a59bbd8a0258b08676fdd6e/src/plugin/web_app_factory_luna.cc#L41-L56
Oct 17 10:11:03 <Herrie> And some here: https://github.com/webosose/luna-surfacemanager/blob/70acbffe6dd8c8a045cd8e6c318fe76727dac1bb/base/qml/WebOSCompositorBase/models/SystemUIWindowModel.qml
Oct 17 10:11:59 <Tofe> Herrie: you can see it's passed on here: https://github.com/webosose/wam/blob/master/src/platform/web_app_wayland.cc#L183
Oct 17 10:12:44 <Tofe> We also use it in our cardshell, for detecting JustType
Oct 17 10:15:01 <Tofe> ^ ( here: https://github.com/webOS-ports/luna-next-cardshell/blob/herrie/qt6/qml/LaunchBar/Launcher.qml#L242 )
Oct 17 10:18:43 <Herrie> It could be we need to add an option, since WAM somehow assumes everything is fullscreen? At least I guess it does on TV's somehow?
Oct 17 10:19:09 <Herrie> The card concept doesn't exist on TV's, at least I haven't seen it as such
Oct 17 10:19:27 <Tofe> right; however, even when fullscreen, DPI should matter
Oct 17 10:20:46 <Tofe> The "resolution" field in appinfo.json is actually taken into account, but not the way we'd like: if present, the wayland window will be of the size specified by "resolution", and then scaled to fit our card
Oct 17 10:21:02 <Tofe> so it's not a DPI management here, just some scaling
Oct 17 10:41:51 <Herrie> Tofe: OK.
Oct 17 12:19:58 <Tofe> https://github.com/webosose/chromium91/commit/009b55412e7722aedd705ead59dcab12500e1dfd I think it corresponds to the scaling I was talking about
Oct 17 12:38:00 <Tofe> Maybe related to https://bugs.chromium.org/p/chromium/issues/detail?id=910797#c9 ?
Oct 17 12:57:37 <Tofe> It looks things are a bit shady when the device scale factor (i.e. screen DPI reported by the compositor) differs from the device pixel ratio (i.e. DPI for the web rendering)
Oct 17 15:09:36 <Herrie> Tofe: Well that's for neva media, which is media playback
Oct 17 15:09:40 <Herrie> Could be we need to adjust it so it does the same for web apps?
Oct 17 15:10:16 <Tofe> Could be yes
Oct 17 15:11:04 <Herrie> This code seems to have some IF specific for neva media, which is only used for media playback. At least that's how I read it
Oct 17 15:11:50 <Tofe> That's also how I read it yes; they've added some "additional scaling" dedicated to media
**** BEGIN LOGGING AT Mon Oct 17 20:51:42 2022
**** ENDING LOGGING AT Tue Oct 18 02:59:57 2022