Splash widget size settings are ignored

Question

I'm simply configuring the out of box splash screen widget.  No matter which size setting I use -- percentage or custom pixel settings - the splash screen shows up at 100%.  It covers the entire app. How do I fix this?  [Am not a first time users.  I've built a dozen or so apps.  Have googled around for similar instances and a solution but found nothing. )   Thanks.

DavidKnudsen · Answer

I can provide clues about what causes this to happen, but I haven't found a solution yet. It has to do with font scaling that takes place outside of AGOL. The two common causes are that the browser zoom level is not default and that the Windows "Scale and layout" display setting is not set to 100%. Laptops are often affected by the latter, as Windows defaults to scaling by 125% or 150%. Browser scaling is typically triggered by the user, either intentionally (to make small text easier to read) or accidentally (there are keyboard shortcuts that can do this--Ctrl-+, Ctrl--, and Ctrl-0). When you set scaling to 100% in both of these environments, the splash widget will likely behave as configured.

ColinCampbell1 · Answer

Hi Molly,

Unfortunately I haven't yet found a solution in Web App Builder, but I've found an alternative route that I might go down. It looks like it's fairly easy to create a splash window in Experience Builder, so I'm thinking I might create a very simple Web Experience (essentially a single page with my existing Web App embedded in it) and then put a splash screen on top of it.  It's not as neat as having it done in one app and may not work in every circumstance, but I don't think my users will notice a bit.  I should say that I haven't actually got around to doing it yet, but from the webpage below it definitely sounds possible.

Cheers

Colin

https://community.esri.com/ideas/18348

MollyJordan · Answer

Colin -

Did you ever find a solution to this problem? I am currently having the same issue and would like to solve before deployment to end users. However, this is the only thing information I can find on this issue.

Thanks,

Molly