Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions app/views/shared/_email_languages.html.erb
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ locals:
),
locale,
checked: selection ? selection.to_s == locale.to_s : I18n.locale.to_s == locale.to_s,
lang: locale,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have lang above on line 28 as well. Do we need both?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 32 puts the attribute on the element while 28 puts it on the <span> attribute itself. Right now, if a user activates the read-all feature, it will read both the input and the text in the set languages.

The fact that this is happening should be discussed further and that is why I wrote LG-9949. There have been previous discussions on whether or not similar behaviors are priority fixes. So for now, I think we both.

]
end,
) %>