Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#33091 closed defect (bug) (fixed)

1Password thinks the text "log in" a form should trigger a password save

Reported by: markjaquith's profile markjaquith Owned by: markjaquith's profile markjaquith
Milestone: 4.3 Priority: high
Severity: normal Version: 4.3
Component: Upgrade/Install Keywords: needs-patch
Focuses: Cc:

Description

This is really weird, but if you have a plain, unlinked, un-evented paragraph like this in a form:

<p>There's a frog on the bump on the log in the bottom of the sea</p>

and you also have a password filled in somewhere in the form...

and you click the word "frog" in that sentence...

1Password will prompt you to save the password, because it thinks you're submitting the form. YEAH.

So... in our install screen:

You will need this password to log in, please store it in a secure location.

I'm suggesting we do:

You will need this password to log&nbsp;in, please store it in a secure location.

Which fools 1Password.

Attachments (2)

32091.diff (752 bytes) - added by markjaquith 10 years ago.
33091.2.diff (671 bytes) - added by SergeyBiryukov 10 years ago.

Download all attachments as: .zip

Change History (11)

@markjaquith
10 years ago

#1 @markjaquith
10 years ago

  • Owner set to markjaquith
  • Resolution set to fixed
  • Status changed from new to closed

In 33387:

Prevent 1Password from thinking the text "log in" should trigger a password save prompt

fixes #33091

#2 follow-up: @boonebgorges
10 years ago

This is the weirdest thing ever. Do we know whether 1Password is going to do the same thing in other languages? Should there be a translator note to that effect?

#3 in reply to: ↑ 2 @DrewAPicture
10 years ago

  • Keywords 2nd-opinion added
  • Resolution fixed deleted
  • Status changed from closed to reopened

Replying to boonebgorges:

This is the weirdest thing ever. Do we know whether 1Password is going to do the same thing in other languages? Should there be a translator note to that effect?

Was just going to suggest at least a translator comment to indicate why the non-breaking space is in there. So +1 for a translator comment. @ocean90: Thoughts?

#4 @markjaquith
10 years ago

Translator's note could work. No idea what the trigger phrases are in other languages.

Also: https://twitter.com/1Password/status/624241718897078274

#5 @SergeyBiryukov
10 years ago

33091.2.diff adds a translator comment. Suggestions for the text are welcome.

#6 @markjaquith
10 years ago

@SergeyBiryukov — wouldn't have phrased it differently myself! Look good except for the lack of a closing PHP tag. ;-)

#7 @markjaquith
10 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In r33437:

Add a translator note for the fix in r33387

props SergeyBiryukov
fixes #33091

#8 @ocean90
10 years ago

  • Keywords needs-patch added; 2nd-opinion removed
  • Resolution fixed deleted
  • Status changed from closed to reopened

The translator comment needs to be directly before the string. It's currently assigned to the "Important:" string.

#9 @SergeyBiryukov
10 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 33441:

Move the translator note added in [33437] directly before the string it applies to.

fixes #33091.

Note: See TracTickets for help on using tickets.