(no longer active) Reporter
	Description • 11 years ago

See the discussion in bug 850346.

	Mounir Lamouri (:mounir) Assignee
	Comment 1 • 11 years ago

Passed try: https://tbpl.mozilla.org/?tree=Try&rev=e06ebfad4782

	Mounir Lamouri (:mounir) Assignee
	Comment 2 • 11 years ago

We should ideally push that to Aurora and Beta to reduce the exposition of this attribute.

	Alex Keybl [:akeybl]
	Comment 3 • 11 years ago

Is 21 really affected by bug 850346? Why are we backing this out (or preffing this off) only in time for the last Beta if FF21 is affected?

	Mounir Lamouri (:mounir) Assignee
	Comment 4 • 11 years ago

https://hg.mozilla.org/integration/mozilla-inbound/rev/68869162af7c

bug 850346 doesn't have much to do with that, I'm not sure what you are trying to ask here.

	Mounir Lamouri (:mounir) Assignee
	Comment 5 • 11 years ago

Comment on attachment 742845 [details] [diff] [review]
Patch

[Approval Request Comment]
Regression caused by (bug #): bug 746142
User impact if declined: some websites might use the feature and got broken later
Testing completed (on m-c, etc.): just landed in m-i, tests are in m-c
Risk to taking this patch (and alternatives if risky): we should push this patch ASAP to release so we reduce the chances of having anyone using this feature before it is ready to be used.
String or IDL/UUID changes made by this patch: changed HTMLInputElement.webidl, no UUID changes.

	Mounir Lamouri (:mounir) Assignee
	Comment 6 • 11 years ago

To give some context about why this feature is being restricted to Nightly and Aurora: we are not sure what are the attributes we want, Hixie specified different things from what we implemented and I now have a new set of values I would like us to support. We should only make the feature available in release when we will actually be willing to support it forever.

	bhavana bajaj [:bajaj]
	Comment 7 • 11 years ago

Comment on attachment 742845 [details] [diff] [review]
Patch

Its too late to get in in FX20 (release now) as we ~2weeks away from shipping Fx21.Approving on beta/aurora.

Please land on mozilla-beta asap so that this can get into our final beta.Do we need any QA testing here for verification?

	Phil Ringnalda (:philor)
	Comment 8 • 11 years ago

https://hg.mozilla.org/mozilla-central/rev/68869162af7c

	Mounir Lamouri (:mounir) Assignee
	Comment 9 • 11 years ago

(In reply to bhavana bajaj [:bajaj] from comment #7)
> Comment on attachment 742845 [details] [diff] [review]
> Patch
> 
> Its too late to get in in FX20 (release now) as we ~2weeks away from
> shipping Fx21.Approving on beta/aurora.

Thanks :) I didn't actually mean to ask approval-release. Second time that happened to me ;)

> Please land on mozilla-beta asap so that this can get into our final beta.Do
> we need any QA testing here for verification?

Yes, that would be great.

	Ryan VanderMeulen [:RyanVM]
	Comment 10 • 11 years ago

https://hg.mozilla.org/releases/mozilla-aurora/rev/a27b593bf117

This is going to need a beta-specific patch.

	bhavana bajaj [:bajaj]
	Comment 11 • 11 years ago

needsinfo on :mounir to help with comment# 10 as this needs to happen by Friday EOD PT to be ready for our final beta also can you explain what QA verification is needed here? Anything else in addition to making sure the pref is false by default ?

	Mounir Lamouri (:mounir) Assignee
	Comment 12 • 11 years ago

https://hg.mozilla.org/releases/mozilla-beta/rev/35a57e9f45a4

We don't have webidl on Beta so I didn't touch the idl to not make people go mad so the pref basically just disable the behaviour.

Regarding testing, QA could check that regular keyboard shows on (on Fx Android Beta) when focusing things in that file:
http://oldworld.fr/mozilla/inputmode.html

On Aurora/Nightly (Fx Android), some special keyboards should show up.

	Kohei Yoshino
	Comment 13 • 11 years ago

I've added this bug to the compatibility doc. Please correct the info if wrong.
https://developer.mozilla.org/en-US/docs/Site_Compatibility_for_Firefox_21

	Kevin Brosnan [Ex-Mozilla]
	Comment 14 • 11 years ago

Verified that using 21 beta 7 it is disabled

Verifed that using Aurora 22 and Nighty 23 it is enabled.

Is there any difference between titlecase and autocapitalized? Both resulted in text that only the first character was capitalized. Title case I would expect every word to be capitalized. I am unsure about autocapitalized behavior. The whatwg docs do not seem to provide guidance for these attributes http://www.whatwg.org/specs/web-apps/current-work/#attr-fe-inputmode

	Mounir Lamouri (:mounir) Assignee
	Comment 15 • 11 years ago

Kevin, titlecase should uppercase every first character and autocapitalized should uppercase every first character of a sentence. The former should produces "Foo Bar. Foobar." and the later "Foo bar. Foobar.".

	Mounir Lamouri (:mounir) Assignee
	Comment 16 • 11 years ago

(In reply to Mounir Lamouri (:mounir) from comment #15)
> Kevin, titlecase should uppercase every first character and autocapitalized
> should uppercase every first character of a sentence. The former should
> produces "Foo Bar. Foobar." and the later "Foo bar. Foobar.".

Sounds good. Thanks :)