Skip to content

Question entry l10n fixes - #7790

Open
denyshon wants to merge 1 commit into
mozilla:mainfrom
denyshon:fix-question-entry-l10n
Open

Question entry l10n fixes#7790
denyshon wants to merge 1 commit into
mozilla:mainfrom
denyshon:fix-question-entry-l10n

Conversation

@akatsoulas
akatsoulas requested a review from escattone August 14, 2026 14:09

@escattone escattone left a comment

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.

Thanks @denyshon!

Needs a rebase on main to remove the merge conflicts. I can do that as well if you'd prefer.


a.question-entry--meta-item,
.question-entry--meta-item a {
color: inherit;

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.

This changes ensures that the color rule below for .question-entry--meta-bold won't be used, due to specificity. Adding the following somewhere in this file will fix that:

a.question-entry--meta-bold {
  color: var(--color-heading);
}

gap: p.$spacing-xs;
color: inherit;
text-decoration: none;
white-space: nowrap;

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.

This means that all "meta" chips no longer wrap, which means that long product or topic titles, or long usernames won't wrap on narrow mobile views, forcing the user to horizontal scroll. On the other hand, it's nice to keep those chips together (unbroken), which I think is your intention. Just noting that.

{% elif obj.channel == "direct_support" and obj.zd_updated_at and obj.zd_updated_at != obj.created %}
<span class="question-entry--meta-item">
{{ _('Updated') }}
<time datetime="{{ obj.zd_updated_at.isoformat() }}">

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.

Do we want to lose the time element? These times will no longer be machine readable, or at least no longer more easily machine readable.

b_open='<span class="question-entry--meta-bold">'|safe, b_close='</span>'|safe,
when=obj.last_answer.created|timesince,
a_open='<a href="'|safe + obj.last_answer.get_absolute_url() + '" rel="nofollow">'|safe, a_close='</a>'|safe %}
{{ b_open }}{{ name }}{{ b_close }} replied {{ a_open }}{{ when }}{{ a_close }}

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.

Maybe add an L10N comment for this?

</svg>
{% if user_is_contributor and not profile_username %}
{{ _('asked by') }} <a class="question-entry--meta-asked-by"
{{ _('asked by') }} <a class="question-entry--meta-bold"

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.

Should this get the same treatment as replied below, so it's no longer a L10N fragment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants