Problem/Motivation

1. Missing paddings on the highlighted node container.
2. The article image sticks out of the highlighted area.

See attached screenshot.

Proposed resolution

I think we need to find a different way to indicate that a viewed node is unpublished.

Issue fork drupal-3323028

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Chi created an issue. See original summary.

enaznin’s picture

Assigned: Unassigned » enaznin

enaznin’s picture

Version: 10.0.x-dev » 10.1.x-dev
enaznin’s picture

Added padding and max-width to the image inside the node so it doesn't break. Attached before after screenshot.

enaznin’s picture

FileSize
1.73 MB

_pratik_ made their first commit to this issue’s fork.

enaznin’s picture

Status: Active » Needs review
smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs subsystem maintainer review

I think we need to find a different way to indicate that a viewed node is unpublished.

What was agreed upon to do that?

Will need approval from olivero maintainer also.

enaznin’s picture

Assigned: enaznin » Unassigned
andy-blum’s picture

Title: Olivero: Unpublished nodes look weird » Olivero: Update styles for unpublished nodes
Priority: Normal » Minor

1. Missing paddings on the highlighted node container.
2. The article image sticks out of the highlighted area.

The padding of unpublished nodes matches the padding of published nodes, and the article images are supposed to overflow the boundaries, per the design. We don't really want published/unpublished nodes to be dramatically visually different. I'm not opposed to finding a better "less weird" set of styles, but unless there's a real usability issue that warrants it, I don't think this ticket is really worth pursuing.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.