Thanks for the feedback everybody!
On Thursday, March 7, 2019 at 9:15:45 AM UTC, Jeremy Ruston wrote:
>
> I believe that the problem here is browser security: they think nobody
> would want a website that fullscreens itself without permission when it
> opens, and so they implement a restriction
I believe that the problem here is browser security: they think nobody would
want a website that fullscreens itself without permission when it opens, and so
they implement a restriction whereby fullscreen can only be entered within a
user-triggered event handler (e.g. a button).
Best wishes
Je
Hi Adam,
unfortunately, the simple answer to this is: `tm-full-screen` will never
work as a startup action, as these actions run before the rootwidget is
initialized to listen for and handle these messages.
It could work if you figure out a way to delay the action, but I'm not
sure how one w
Hi Adam,
I've been successfully using startup actions to manipulate variables, set
fields, create tiddlers etc. but the one thing I still could not get it to
action are widget messages, like tm-full-screen. I'm not quite sure why.
For the record, the above code could be simplified to this. It s
Hi Hubert,
Just wanted to see if you ever got this to work. I'm running into a similar
problem at the moment with StartupActions. I could use a bit of insight
into its workings.
Best wishes,
Adam
On Wednesday, June 27, 2018 at 11:27:07 AM UTC+1, Hubert wrote:
>
> Hi,
>
> I'm trying to make us
5 matches
Mail list logo
