Re: On longstanding webcompat issue about padding-bottom/padding-right missing in scroll containers

> Could you please summarize what the table ends up looking like after these changes? Good idea! I update the table in https://github.com/w3c/csswg-drafts/issues/129#issuecomment-808526584 > I also saw bz note that we only want to change our behavior once in this area, but I guess since this has

On longstanding webcompat issue about padding-bottom/padding-right missing in scroll containers

Over the years, we accumulate a lot of duplicates in Bug 748518 about `overflow:auto/scroll` container's padding-bottom / padding-right is missing in Firefox when scrolling to the bottom / right. Blink and WebKit have this behavior for most

Intent to unship: -moz-prefixed multi-column properties and -moz-column-gap

ixed properties back. Ting-Yu Lin (:TYLin) [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1308636 [2] https://drafts.csswg.org/css-multicol-1/ [3] https://drafts.csswg.org/css-align-3/#propdef-column-gap [4] https://groups.google.com/d/msg/mozilla.dev.platform/p80ptKoqVvk/uKJwoK6JDAAJ [5] https:/

Intent to ship: CSS column-span property

-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

Re: Intent to ship: CSS Shapes Module Level 1 (partial)

Thank you for all the feedback. I feel the safest plan is to ship the entire module at once. It also saves some work to implement two preferences to exclude the shape-outside: value which we don't render in the first stage. I'm implementing "shape-outside: ", and will do "shape-margin" after

Intent to ship: CSS Shapes Module Level 1 (partial)

CSS Shapes Module Level 1 [1] defines three properties: "shape-outside", "shape-margin", and "shape-image-threshold" (used with shape-outside: ), which allows the users to define non-rectangular shapes for floating elements. See the previous discussion for the main bug, pref, and examples in the

Intent to implement: CSS shape-outside property

*Summary*: CSS shape-outside property could be used on float element to define a non-rectangular area like circle, ellipse, or arbitrary polygon shape such that text or inline elements could flow around it. See Jen's demo for examples. *Bug*:

Re: Intent to Ship: HTML5 and tags

On Wed, Apr 20, 2016 at 2:44 AM, Tantek Çelik <tan...@cs.stanford.edu> wrote: > On Tue, Apr 19, 2016 at 8:41 AM, Ting-Yu Lin <t...@mozilla.com> wrote: > > To summarize the feedback so far, I'd still like to ship and > > without |summary::marker| because > >

Re: Intent to Ship: HTML5 and tags

| to add more css rules. Ting-Yu On Thu, Apr 14, 2016 at 3:53 PM, Ting-Yu Lin <t...@mozilla.com> wrote: > As of Firefox 48 I intent to ship HTML5 and tags on > all platforms. The features has been developed behind pref > "dom.details_element.enabled", and had been ena

Re: Intent to Ship: HTML5 and tags

On Tue, Apr 19, 2016 at 10:15 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 4/19/16 1:09 AM, Ting-Yu Lin wrote: > >> Yes. supports the same set of "list-style-type" property values >> as because our default style for is "display: list-item"

Re: Intent to Ship: HTML5 and tags

On Tue, Apr 19, 2016 at 11:02 AM, Karl Dubost <kdub...@mozilla.com> wrote: > > Le 14 avr. 2016 à 18:24, Ting-Yu Lin <t...@mozilla.com> a écrit : > > On Thu, Apr 14, 2016 at 5:03 PM, Xidorn Quan <quanxunz...@gmail.com> > wrote: > >> Shouldn't "summary

Re: Intent to Ship: HTML5 and tags

On Tue, Apr 19, 2016 at 12:03 AM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 4/14/16 3:53 AM, Ting-Yu Lin wrote: > >> One major concern in the "intent to implement" discussion is the ability >> to >> style the summary disclosure triangle. Currently

Re: Intent to Ship: HTML5 and tags

On Thu, Apr 14, 2016 at 5:03 PM, Xidorn Quan <quanxunz...@gmail.com> wrote: > On Thu, Apr 14, 2016 at 6:51 PM, Ting-Yu Lin <t...@mozilla.com> wrote: > >> On Firefox: >> summary::-moz-list-bullet { list-style-type: none; } OR summary { >> display: block; } &

Re: Intent to Ship: HTML5 and tags

> No other implementation supports ::marker either, right? If that is > correct, it seems fine to me to perfect styling support in a later > release. Yes. Currently, no other vendor support ::marker. > Do other browsers support styling the disclosure triangle? Chrome and Safari could style the

Intent to Ship: HTML5 and tags

gzilla.mozilla.org/show_bug.cgi?id=205202>). If not, we can ship it in Firefox 48. Otherwise this feature might skip one or two releases. Please give me some feedbacks. Thanks. Ting-Yu Lin (:TYLin) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Submit to MozReview using Git

> ~/repo/gecko/gecko-dev master$ git mozreview configure > searching for appropriate review repository... > warning: error trying to resolve Mercurial changesets I saw the same error before. After setting mozilla-central in my git repo remote described in the following wiki, I can setup review

Intent to Implement: HTML and tags

Summary: The is used as a disclosure widget from which the user can obtain additional information or controls. is used as a summary or legend of the details. To expand the details, the user could click on the summary or by adding a bool attribute 'open' to the details. An example: Open the

Re: PSA: New reftest analyzer keyboard shortcuts

kats, keyboard shortcuts are convenient. BTW, I filed bug 1187774 and added some thoughts for making the keyboard shortcuts discoverable. TYLin On Fri, Jul 24, 2015 at 9:37 PM, Kartikaya Gupta kgu...@mozilla.com wrote: Since keyboard shortcuts aren't very discoverable this is just a note to

Re: Hash table iterators, and a call for help

It might be worth to mention the PLDHashTable::Iterator in the hashtable guides. https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Guide/Hashtables https://developer.mozilla.org/en-US/docs/Detailed_XPCOM_hashtable_guide TYLin On Mon, Jul 13, 2015 at 1:36 PM, Nicholas Nethercote

Re: Git - Hg workflows?

I cannot live without moz-git-tools. Let me explain. a) Landing code to inbound, fx-team, aurora, etc I use git bz attach to attach patches to bugzilla and use checkin-needed. b) Pushing to Try I use git push-to-try. This command needs a local hg repo, so I need to update it every time when