Policy for new configuration options

David Rosca nowrep at gmail.com
Tue Mar 19 18:21:38 GMT 2019


Hi,

On Mon, Mar 18, 2019 at 10:44 PM Jukka Ruohonen <jruohonen at iki.fi> wrote:
>
> Hello,
>
> I wonder whether the Falkon team has a design policy (or philosophy) for
> adding new configuration options via the user interface?

Usually the policy is if there is a valid reason to make it
configurable, it is configurable.
>
> For various reasons, I would like to disable some options. The examples
> include but are not limited to:
>
>         allowJavaScriptAccessClipboard
>         allowJavaScriptPaste
available from Preferences -> Privacy -> JavaScript

>         LocalContentCanAccessRemoteUrls
always on (we need it for our internal pages)
>         screenCaptureEnabled
always off - may be a good idea to allow it when implementing
QWebEnginePage::DesktopAudioVideoCapture feature request
>         DisableVideoAutoPlay
available from Preferences -> Browsing
>         webGLEnabled
always on - don't really see reason to turn it off
>         DNSPrefetch
available from Preferences -> Browsing
>         AutoLoadIconsForPage
always on - we need it
>
> Of course, I can also patch a local copy easily.
>
> - Jukka

David



More information about the Falkon mailing list