Intent to ship: <link rel=preload ...>

[Dragana Damjanovic]

As of Firefox 56, I intent to ship link rel=preload. The feature is
developed in bug 1222633 <
https://bugzilla.mozilla.org/show_bug.cgi?id=1222633>. There is no pref for
this feature, so it will be shipped directly.

**Bug to turn on by default**:
https://bugzilla.mozilla.org/show_bug.cgi?id=1222633

**Link to standard**:
https://w3c.github.io/preload/ (This is still a draft)

dragana

[Josh Matthews]

Why is there no preference to control it? I thought that was standard
practice for new features to make it easier to unship them if we
discover a problem that makes it difficult to back out.

Cheers,
Josh

[Michael Layzell]

This also seems like a feature which some users may want to disable, for
example in order to reduce bandwidth usage on certain websites (I'm not
sure how bad the impact would be bug *shrug*).

I imagine we should add a pref if possible before shipping this feature.

On Mon, Jul 31, 2017 at 1:25 PM, Josh Matthews <jo...@joshmatthews.net>
wrote:

> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>

[Dragana Damjanovic]

Sorry, that was my mistake. Of course preload has a pref:

network.preload

My apologies, I was writing e-mail in a hurry.

The pref was implemented in
https://bugzilla.mozilla.org/show_bug.cgi?id=1222633.
The <link rel=preload> is turn on by default and we are planning to ship it
turned on.

dragana


On Mon, Jul 31, 2017 at 7:32 PM, Michael Layzell <mic...@thelayzells.com>
wrote:

> This also seems like a feature which some users may want to disable, for
> example in order to reduce bandwidth usage on certain websites (I'm not
> sure how bad the impact would be bug *shrug*).
>
> I imagine we should add a pref if possible before shipping this feature.
>
> On Mon, Jul 31, 2017 at 1:25 PM, Josh Matthews <jo...@joshmatthews.net>
> wrote:
>