Corey Ford [:coyotebush] Assignee
	Description • 11 years ago

The initial implementation of sticky positioning in bug 886646 hides it behind the preference "layout.css.sticky.enabled". Once the implementation is more complete, this preference should be enabled by default.

	Corey Ford [:coyotebush] Assignee
	Comment 1 • 11 years ago

It's been pointed out to me that we likely shouldn't enable the preference by default in release versions, at least, until the specification is better standardized. So maybe once those blocking bugs are fixed it should be enabled only #ifndef RELEASE_BUILD ?

	Daniel Holbert [:dholbert]
	Comment 2 • 11 years ago

That sounds reasonable. (That's what we did for @supports when its spec was under-development, in bug 814530. The patch here should probably look very much like the patch on that bug.)

	David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)
	Comment 3 • 11 years ago

One other interesting issue mentioned in https://code.google.com/p/chromium/issues/detail?id=145027 is whether there's something interesting to say or fix about nested position:sticky elements.

	Corey Ford [:coyotebush] Assignee
	Comment 4 • 11 years ago

(In reply to David Baron [:dbaron] (needinfo? me) (busy through Sept. 14) from comment #3)
> nested position:sticky elements

work just fine in Gecko and WebKit. (Perhaps a sticky-top header inside a sticky-bottom section, though I'm not certain where that would realistically be useful.)

	Corey Ford [:coyotebush] Assignee
	Comment 5 • 11 years ago

Predictably enough, this is the patch to do that.

	Daniel Holbert [:dholbert]
	Comment 6 • 11 years ago

Comment on attachment 803981 [details] [diff] [review]
Enable position:sticky on Nightly and Aurora.

r=me

Did you still want to wait for the blocking bugs to be fixed before landing this, per comment 1, or did you want to land this sooner?

(Seems like we might as well wait, since it looks like they're close to being fixed, but I'm open to just landing this, too.)

	Corey Ford [:coyotebush] Assignee
	Comment 7 • 11 years ago

Yeah, might as well wait for those.

	Corey Ford [:coyotebush] Assignee
	Comment 8 • 11 years ago

A final try run to make sure this doesn't break anything else:
https://tbpl.mozilla.org/?tree=Try&rev=c29ac5d62b81

	Daniel Holbert [:dholbert]
	Comment 9 • 11 years ago

[needinfo=me to make sure this gets landed after the Try run completes.]

	Daniel Holbert [:dholbert]
	Comment 10 • 11 years ago

The bugs marked as blocking this have now landed, so I landed this:
 https://hg.mozilla.org/integration/mozilla-inbound/rev/2d033c301dfd

(I also clarified the commit message slightly, to avoid giving the impression that this is enabling position:sticky in _current_ Aurora builds.)

	Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)
	Comment 11 • 11 years ago

https://hg.mozilla.org/mozilla-central/rev/2d033c301dfd

	Jean-Yves Perrier [:teoli]
	Comment 12 • 10 years ago

The compat table of
https://developer.mozilla.org/en-US/docs/MDN/Contribute/Tools_with_restricted_access
has been updated.
https://developer.mozilla.org/en-US/Firefox/Releases/27#CSS , too.