Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
MIME-Version: 1.0
Sender: dvpdiner2@gmail.com
In-Reply-To: <CAEwnObBm+7UusWAFpzbmjrKUwwxOnfGK5=BfzW2HMbEe1Ziefw@mail.gmail.com>
References: <29D136F7-E86F-4460-9235-0D6297C95EAE@intel.com>
	<989900075.515434.1462982906494.JavaMail.yahoo@mail.yahoo.com>
	<SN2PR03MB233506814891792A1719F245C3720@SN2PR03MB2335.namprd03.prod.outlook.com>
	<CAEwnObBm+7UusWAFpzbmjrKUwwxOnfGK5=BfzW2HMbEe1Ziefw@mail.gmail.com>
Date: Wed, 11 May 2016 12:36:32 -0700
Message-ID: <CA+z8NA-dn4=Zp+SQTuSoL1+8KjH_rdFpqgyg61CJqordcEeujw@mail.gmail.com>
Subject: Re: proposal for new core plugin to control screen orientation
From: Darryl Pogue <darryl@dpogue.ca>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=001a113faafeafc7fa053296284f
archived-at: Wed, 11 May 2016 19:36:38 -0000

--001a113faafeafc7fa053296284f
Content-Type: text/plain; charset=UTF-8

I think this is a good feature to have as a supported core plugin, but I
also worry about feature creep and endless bikeshedding like we see with
the statusbar plugin.

The originally linked plugin acts as a polyfill for the W3C spec[1]. This
new core plugin should do the same, and should ruthlessly defend that
stance:
*Any feature that falls outside the scope of a polyfill should not be
implemented, nor considered a bug against the plugin.* Instead it should be
filed as a bug on the W3C spec.

[1]: https://www.w3.org/TR/screen-orientation/

On 11 May 2016 at 12:29, Kerri Shotts <kerri@photokandy.com> wrote:

> +1; Agree. I've seen many questions about controlling orientation, so
> having a core plugin to reply with would be nice to have.
>

--001a113faafeafc7fa053296284f--