Re: Intent to unship:

On 6/14/19 7:02 AM, Henri Sivonen wrote: Thanks for the removal. Do we have enterprise Web developer-facing documentation on 1) how TLS client cert enrollment should work now or 2) if there is no in-browser client cert enrollment path anymore, what concretely should be used instead? For what i

Re: Intent to implement and ship: overflow-block and overflow-inline CSS properties

On 6/14/19 6:23 AM, violet wrote: Preference behind which this will be implemented: layout.css.overflow-logical.enabled Thank you. -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to unship:

Client certificates are manually importable in about:preferences > Privacy & security > View Certificates > import Not much has changed since this article: https://www.jscape.com/blog/firefox-client-certificate however we should improve our support articles before this lands in release. On Fri, Ju

Re: Intent to unship:

On Fri, Jun 14, 2019 at 1:24 PM Jonathan Kingston wrote: > Most of the use cases are resolved by web crypto or u2f. Thanks for the removal. Do we have enterprise Web developer-facing documentation on 1) how TLS client cert enrollment should work now or 2) if there is no in-browser client cert enr

Re: Intent to implement and ship: overflow-block and overflow-inline CSS properties

Preference behind which this will be implemented: layout.css.overflow-logical.enabled Enabled by default. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Intent to unship:

has been removed in Chrome since version 56 in Jan 2017 and never was implemented in Internet Explorer or Edge. The element has also been removed from the HTML specification: https://github.com/w3c/html/issues/43 Firefox's implementation never matched the specification completely as the parser cha