Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Compat: remove parenthesis around No; add title attribute #230

Merged
merged 2 commits into from
Jul 10, 2017
Merged

Compat: remove parenthesis around No; add title attribute #230

merged 2 commits into from
Jul 10, 2017

Conversation

Elchi3
Copy link
Member

@Elchi3 Elchi3 commented Jul 7, 2017

"No" is currently rendered as "(No)". The parenthesis only make sense for "(Yes)" and we never had them for "No". Adding title tooltips to further clarify the meanings as well.

Copy link
Contributor

@jwhitlock jwhitlock left a comment

Choose a reason for hiding this comment

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

👍 Looks good. There are some changes that we could make at the same time, or in new PRs.

@@ -103,10 +103,12 @@ function getVersionString(versionInfo) {
style="color: rgb(255, 153, 0);">${localize(compatStrings, 'supportsShort_unknown')}</span>`;
break;
case true:
return `<span style="color: #888">(${localize(compatStrings, 'supportsShort_yes')})</span>`;
return `<span title="${localize(compatStrings, 'supportsShort_yes_title')}"
style="color: #888">(${localize(compatStrings, 'supportsShort_yes')})</span>`;
Copy link
Contributor

Choose a reason for hiding this comment

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

@stephaniehobson: ⚠️ inline style alert ⚠️

Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be "(Yes)" in English and "«Да»" in Russian? In other words, should we move the parentheses inside the translated string?

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated!

break;
case false:
return `<span style="color: #f00">(${localize(compatStrings, 'supportsShort_no')})</span>`;
return `<span title="${localize(compatStrings, 'supportsLong_no')}"
style="color: #f00">${localize(compatStrings, 'supportsShort_no')}</span>`;
Copy link
Contributor

Choose a reason for hiding this comment

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

@stephaniehobson : ⚠️ inline style alert ⚠️

@stephaniehobson
Copy link
Contributor

Hopefully these inline styles will go away when we switch to the new compat tables :)

@jwhitlock jwhitlock merged commit ae1cafb into mdn:master Jul 10, 2017
jwhitlock added a commit to jwhitlock/kuma that referenced this pull request Jul 10, 2017
* mdn/kumascript#213 - CommunityBox, DiscussionList: Discourse
* mdn/kumascript#222 - SpecName, Spec2: GamepadExtensions
* mdn/kumascript#223 - Add folder for no macros test
* mdn/kumascript#224 - AddonSidebar: Submit an add-on link
* mdn/kumascript#225 - Compat: Alpha-sort browsers
* mdn/kumascript#226 - make lint and linting changes
* mdn/kumascript#228 - CompatNo: Add Dutch translation
* mdn/kumascript#230 - Compat: Remove parens around No, title
* mdn/kumascript#231 - Glossary: Add Ukranian support
* mdn/kumascript#232 - AddonSidebar: De-emphasise legacy addons
@Elchi3 Elchi3 deleted the compat-yes-no branch July 25, 2017 12:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants