Reply to thread

Ya, I wasn't necessarily talking about defaulting it to None, rather just have a default that is set at the application level whatever that may be (so you don't need to worry about the future where browsers change what the default is).  But ya, was just a thought off the time of my head... wasn't aware it caused the issues with Safari/WebKit, so... ignore.    The ability for a site to set a default via $config was a different thing (and would be useful for me personally).