Page 1 of 1
[Implemented] <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Jun 12, 2020 5:14 pm
by Peter
Hello Fred,
please, please, please add this line to the generated index.html:
Code: Select all
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Without this line you cannot load a SpiderBasic-App into a PureBasic WebGadget.
That would be great!
Thanks in advance & Greetings ... Peter
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Thu Jun 25, 2020 6:52 pm
by munfraid
+ 1
This would be useful! And thanks for the tip, Peter - once more!
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 11:40 am
by Fred
Added for next version
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 12:06 pm
by Peter
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 12:49 pm
by the.weavster
Is it planned that SB's output should always be compatible with PB's WebGadget?
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 12:51 pm
by Fred
No, but if it can help, we do it. PB WebGadget() is very old on Windows unfortunately.
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 12:57 pm
by Dirk Geppert
There is another meta attribute that helps improve the user experience on a mobile device.
For example, "meta name=shrink-to-fit=no" prevents zooming into a StringGadget when typing on iOS devices.
Is it only needed for iOS or we can put it for web/android as well ?
Re: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Posted: Fri Aug 26, 2022 1:01 pm
by the.weavster
On second thoughts it's probably best not to as it might handicap SB if an updated WebGadget is not on the roadmap for PB.
