Webapp Creator Queries
-
@arubislander Thanks for that. I was just thinking of customising a webapp which isn't compatible to Morph browser. I tried Webber for that but it was asking for Opera, Chrome, Firefox or Edge still.
On a good note, this newcomer Crimson Browser, which is at it's crude form, at the moment, can make those webapps work! It's very crude but, hopefully, the developer vixlump, can keep on chugging along. I am already using it on one of my webapps which doesn't work with either Morph or Sapot browser. The developer is doing a really good job on that front. Cheers.
-
@TakoR The funny thing is, that all Browsers that run natively on UT, including web apps made by Webber, use the same browser engine as Morph. So if it can be made to work in any one of the browsers, it can also be made to work in a web app.
Looking at the source code for Crimson Browser, the most relevant line I think is the following:
httpUserAgent: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36"Maybe make a web app in Webber and enter the string between quotes in the Custom User-Agent header box.
-
@arubislander Thanks for your reply. I had to search the forum about Webber and found out that there is a 6.0.0 version. was using 5.7.0 from the Open Store, which didn't have a Custom User Agent string entry. I was after the defunct Webapp Creator because of its customisation.
Anyway, the string worked for Morph!
Now, Crimson Browser indicates that it stores site cache locally so logins should persist when the app is closed. That somehow solved the "site is open/logged in in another tab" issue. I tried looking for a setting in Morph but to no avail. Is there any setting that's readily available to do this?
I found that Crimson's persistentStoragePath is set to this:
persistentStoragePath: "/home/phablet/.cache/crimson-browser.lumpology/QtWebEngine"I am not sure if there is a setting in Morph to do store site cache locally to prevent a user from logging in again/or have that webapp is open in another tab issue. What do you think?
-
@TakoR Ah, you are on xenial still. Indeed, in the OpenStore the 6.x version of Webber was only uploaded for Focal.
@TakoR said in Webapp Creator Queries:
Now, Crimson Browser indicates that it stores site cache locally so logins should persist when the app is closed. That somehow solved the "site is open/logged in in another tab" issue. I tried looking for a setting in Morph but to no avail. Is there any setting that's readily available to do this?
Have you personally come across this issue? If so, what was the site? Logins have been persistent for me in Morph on all sites that need it.
Are you sure you have not set Morph to start in private mode by default?
-
@arubislander It's just Wire now that's doing this with Morph. The other sites are doing fine in terms of logging in. It's the same issue with the Wire UT app in the Open Store, where Wire would say that it's open in another tab.
The bug was first exhibited during the first days of Wire's webapp, where it says that, in Chromium-based browsers, the app is open in another tab. The initial workaround was to go to Chromium's dev console and add:
document.cookie = 'app_opened=;expires=Thu, 01 Jan 1970 00:00:01 GMT;Path=/;'It has since been resolved after a few updates.
Now, the bug is showing up on Morph, but not on Crimson. Morph, though, has a more usable interface, at the moment.
The biggest difference I can see is that persistent storage path set by Crimson.
@arubislander said in Webapp Creator Queries:
Are you sure you have not set Morph to start in private mode by default?
Yes, I haven't used private mode in Morph yet. Cheers.
-
@TakoR The setting of the persistent storage path should not make a difference, as when unset it points to the application's cache path by default anyway.
I do not have a Wire account (nor is it immediately obvious how to get one) so I cannot test this, even if I had the time.
Are you able to build a version of Crimson Browser without the cache setting and see if that introduces the bug there too?
-
@arubislander said in Webapp Creator Queries:
I do not have a Wire account (nor is it immediately obvious how to get one) so I cannot test this, even if I had the time.
Yes. The website is also tailored for bigger companies as they want to promote their enterprise comms service. The use of Wire for personal use is free, though.
Even though it's bought by an investor, it remains FOSS to this day.
@arubislander said in Webapp Creator Queries:
Are you able to build a version of Crimson Browser without the cache setting and see if that introduces the bug there too?
Hmmm. Upon trying, when that cache setting is removed, I get the same issue as morph.
When I compared the cache file directory between Morph and Crimson, Crimson has a whole QtWebEngine inside it's cache folder, as pointed by the persistent storage path.
-
@TakoR said in Webapp Creator Queries:
Thanks for the link, will take a look when I get time. Can't promise mich this weekend, though.
@TakoR said in Webapp Creator Queries:
When I compared the cache file directory between Morph and Crimson, Crimson has a whole QtWebEngine inside it's cache folder, as pointed by the persistent storage path.
Yes, it seems Crimson Browser puts its data in a sub directory of the application's .cache directory. But it is puzzling why that should make a difference, unless the Wired site is doing something that only works when it can write to both the cache directory and its parent directory.
-
@arubislander said in Webapp Creator Queries:
Thanks for the link, will take a look when I get time. Can't promise mich this weekend, though.
Welcome. It's pretty interesting how it's implemented. The personal accounts are P2P and were written by the original Skype engineers who preferred privacy, before they were bought by Microsoft and used "cloud servers."
@arubislander said in Webapp Creator Queries:
Yes, it seems Crimson Browser puts its data in a sub directory of the application's .cache directory. But it is puzzling why that should make a difference, unless the Wired site is doing something that only works when it can write to both the cache directory and its parent directory.
It is kind of puzzling especially as to why. Wire, though is known to delay sending if there are compromises with the connection but I don't know how that's related, at the moment. Cheers.
-
Should I create another thread just for Wire @arubislander? This one's originally for the Webapp Creator. Regards,
-