cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Date Fri, 04 Aug 2017 16:19:24 GMT
There is a clear path forward for most plugins. The plugins-next board
has ~60 issues to tackle to sunset, integrate and update 'em all. Lots
of work to do, but it should be healthy for the project.

One thing I wanted to point out is that the decision on the Dialogs
plugin has been waffling (full discussion in the issue [1]).
Initially, we had voted to keep + update to polyfill the HTML <dialog>
element. Turns out there is a Google-written polyfill out there
already [2]. Simon and I think we should switch the decision on this
plugin to "SUNSET", that is, announce that we will no longer be
maintaining the plugin, let the community take it over if they wish,
and toss up a blog post detailing how to transition to the <dialog>
element / leverage the polyfill if necessary.

If you have opinions on this, please chime in on the thread. On Monday
I'll move forward with formalizing the decision/tasks in there.


On Fri, Jul 28, 2017 at 12:57 PM, Filip Maj <> wrote:
> Small update on this topic:
>  - still need to clarify next steps on some of the INTEGRATE plugins
>  - I think the Dialogs plugin's KEEP + UPDATE decision needs a bit of
> clarification as well
>  - I am trying to work with the W3C's web platform tests [1] to
> validate latest spec adherance on the Android and iOS OS versions that
> cordova-android and cordova-ios currently support. For now looking at
> APIs such as the File API and XHR. The reason I am doing this is to
> understand _what_ APIs we still need to polyfill for these
> platforms+versions. Ideally, a lot of these APIs are built in and
> passing the tests, so moving forward we only have to implement the
> minimum set of APIs where support is still wobbly inside cordova. I
> will be reporting these results in the relevant issues per API.
> For those wanting to get the w3c-platform-tests working with cordova,
> I got it working by changing the `host` property in the
> config.default.json file to a local-network IP (e.g.,
> which I use to access the tests from my device), and creating a new
> cordova app that whitelists that IP (on port 8000), and pointing the
> <content src=""> location to that IP + port.
> [1]
> On Tue, Jul 25, 2017 at 9:59 AM, Kerri Shotts <> wrote:
>> Just wanted to say “THANKS!” for the work you’ve done on this! :-) It’s much
>> ~ Kerri
>>> On Jul 22, 2017, at 14:43, Filip Maj <> wrote:
>>> ...

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message