Hello, you can always check out my Dynamic Style extension, which allows to apply custom CSS on a WebViewer’s displayed webpage. A link to it on App Inventor Store:
http://moliata.com/APP-INVENTOR/products/dynamicstyle.php
1 Like
You can get the favicon by setting an image.Picture to YOUR_URL/favicon.ico e.g
http://google.com/favicon.ico
http://youtube.com/favicon.ico
I dont think that is the right way. Because the dev can rename favicon.ico, right?
1 Like
Correct. Every dev can it name how he want.
So this is no solution for all pages.
As example:
https://www.makeroid.io/favicon.ico
Does not work.
I donnu if it possible to get the HTML of the current page, because then you can parse the meta-tag out of it
1 Like
I tried it with makeroid.io but it does not show the correct favicon.
https://www.google.com/s2/favicons?domain_url=http%3A%2F%2Fwww.makeroid.io%2F
https://www.google.com/s2/favicons?domain=www.makeroid.io
Yes, sure he can but most websites still use this because it guarantees favicons to work in internet explorer. The method is now deprecated.
github.com/favicon.ico
twitter.com/favicon.ico
thunkable.com/favicon.ico
puravidaapps.com/favicon.ico
w3schools.com/favicon.ico
stackoverflow.com/favicon.ico
Maybe this is not working only at Makeroid 
1 Like
That’s not true…
https://www.makeroid.io/assets/favicon.ico
That tag guarantees that it works in all browsers
This doesn’t work in old IE
A little question then…
Who uses (old) IE? 
3 Likes
As @Sander suggested, I also think it would be great if we could get the HTML content from the current page open in the webviewer.
Anymore?
In next release, to use WebViewString, you can access it with window.Makeroid object rather than window.AppInventor. If someone wants it to be preserved, then reply here, else it will be renamed.
yes, I would recommend urgently to keep the existing name "AppInventor"
Makeroid is an App Inventor distribution, so why everything changing from App Inventor to Makeroid?
You want to attract developers from App Inventor and other platforms… so why do you want to make it more complicated as necessary to do the switch? (and btw. back again)
this will break all existing WebViewString examples for Makeroid, for example these App Inventor Tutorials | Pura Vida Apps
see also this discussion
https://community.makeroid.io/t/assets-when-using-companion-are-now-saved-at-sdcard-makeroid/925/4?u=taifun
Taifun
1 Like
One reason is because there will be new JS interfaces coming in the next release.
Is there a way that we can handle both?
window.AppInventor & window.Makeroid
yes, we will test
Its simple just add another JavaScript interface called AppInventor while keeping Makeroid too…
What is this for? It is obsolete.