Re: Intent to unship: TLS 1.0 and TLS 1.1

[Martin Thomson]

On Sun, Oct 6, 2019 at 6:35 PM  wrote:

> I would agree that these changes and changes that have already occurred
> over the last year or so, have broken access to admin consoles of older
> networking kit. I had to pull a WinXP machine out of storage recently to
> manage an HP 2610 switch.
>

For the foreseeable future, we will retain the pref
(security.tls.version.min, accessible through about:config) that will allow
individual overrides for this default configuration.  I expect that we will
eventually remove this capability and you will have to go searching for
insecure software so that you can do insecure things.  I appreciate the
pain this causes, but the fact is that the Internet is a sufficiently
hostile environment that all devices connected to it really do need an
up-to-date version of important software, especially networking software.

Ultimately, there isn't a good distinction between devices that are on the
(big "I") Internet and devices that are on (private) networks. For
instance, we don't want to have airport or coffee shop WiFi being able to
access the sorts of exceptions we create for your home network.

If this is sufficiently widespread, we might look into what it would take
to build in some way to override on a per-host basis or carve out
exceptions for private numbering spaces, but we need to be very careful
about opening avenues for attack.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to ship: CSS column-span property

[Patrick Brosset]

Regarding DevTools support: the new value can be found in the CSS values
auto-complete in the Rules panel, so that's great.
But I just wanted to mention the potential inspector feature that could be
built around multicol layouts. We have leading tools when it comes to grid
support, and I think a similar tool could be done for multicol. Something
that highlights the columns, the gaps between them, and the items
(especially useful when items span multiple columns).
Positioning items in a multicol layout is not nearly as complex as doing
the same in a grid layout, so a tool like this is probably not as
important. But still worth considering at some point.

Kudos for shipping this feature btw! Great work.

On Tue, Oct 8, 2019 at 8:32 PM Ting-Yu Lin 林庭宇  wrote:

> As of today, I intend to turn "column-span" on by default for all platforms
> in Firefox 71. It has been developed behind
> "layout.css.column-span.enabled" preference, and has been enabled on
> Nighly-only in bug 1423383.
>
> *Summary: *
> The CSS column-span property, when its value is set to "all" makes an
> element span across all columns in the multi-column layout.
>
> *Bug to turn on by default: *
> https://bugzilla.mozilla.org/show_bug.cgi?id=1426010
>
> *Meta bug where this feature is developed:*
> https://bugzilla.mozilla.org/show_bug.cgi?id=616436
>
> *Standard:*
> https://www.w3.org/TR/css-multicol-1/#column-span
>
> *Platform coverage:*
> Like many other CSS features, column-span has support on all platforms.
>
> *DevTools bug:*
> None. Column-span doesn't require special support from the DevTools.
>
> *Other browsers: *
> According to caniuse.com, Chrome has shipped unprefixed column-span since
> Chrome 50 in 2016, and Safari has shipped this in Safari 9 since 2015.
> https://caniuse.com/#search=column-span
>
> *web-platform-tests: *
> Those tests with title "multicol-span-all-*" in multi-column test suite.
> https://github.com/web-platform-tests/wpt/tree/master/css/css-multicol
>
> *Secure contexts:* N/A
>
> *Note:*
> To support the development of column-span, the architecture of the multicol
> layout needs to be changed in a nontrivial way. If you see any bug, please
> one file under "Layout: Columns" component. Thanks!
>
>
> Ting-Yu Lin
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform