NPM Resource Changed ? ? Pending

User tests: Successful: Unsuccessful:

avatar richard67
richard67
23 Jan 2021

Pull Request for #32070 (comment) issue 1.

Summary of Changes

Remove unwanted padding from menu item edit icons.

Testing Instructions

  1. On a current 4.0-dev branch or latest nightly built with the merged PR #32070 included, install blog sample data if you haven't done that yet, or make sure in some other way to have enough menus at diverse positions to verify the issue and the fix.
  2. Enable frontend editing for menus:
    2021-01-23_06
  3. Login to frontend and go to some other page than the start page to get rid of the big image being shown at the top.
  4. Check horizontal alignment of menu items (in case of a horizontal menu the first one) in menu modules to other modules' content.
    Result: There is some padding before the menu item's edit icon.
  5. Log out so there is no frontend editing and check again alignment, check again horizontal alignment of menu items and note the change in vertical module positions.
    Result: Without frontend editing, menu items are aligned well horizontally with other content. Thing below the header section moved a bit up compared to frontend editing on.
  6. Check the same (steps 4 and 5) for LTR. You can easily change to LTR by editing file language/en-GB/langmetadata.xml and changing <rtl>0</rtl> to <rtl>1</rtl> in the <metadata> section.
    Result: Not that easy to see due to the other issue with the position of the module edit buttons.
  7. Apply the patch of this PR.
  8. Repeat steps 3 to 6.
    Result: See section "Expected result AFTER applying this Pull Request" below.

Actual result BEFORE applying this Pull Request

LTR with frontend editing enabled:

2021-01-23_01

The menu items are not aligned as they would be when frontend editing was switched off, see red lines in the screenshot above and green lines in the one below.

LTR without frontend editing:

2021-01-23_00

The 2 screenshots have been made with the same window size. As you can see by the articles' texts at the bottom, the vertical space needed by the horizontal menu in the header changes when frontend editing is on, so everything below the header moves a bit down.

Expected result AFTER applying this Pull Request

LTR with frontend editing enabled:

2021-01-23_02

Compared to screenshot 2 in the previous section, the vertical positions of things below the header area haven't changed.

The horizontal alignment of menu item edit icons to menu titles or other content is the same as the horizontal alignment of menu item titles without frontend editing e.g. when logged off.

For RTL, the results are harder to verify due to the other issue with position of the module edit buttons.

Additional information

The underline of the menu item edit link in the header section has to be fixed with another PR.

2021-01-23_07

I've tried a bit when doing this PR here but did not really find a nice way. It should be removed completely for the edit icon in _header.scss (and possibly also _footer.scss).

Documentation Changes Required

None.

avatar richard67 richard67 - open - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 23 Jan 2021
Category Front End Templates (site) NPM Change
avatar brianteeman
brianteeman - comment - 23 Jan 2021

This can be done without any special LTR or RTL css

Use padding-inline-start and padding-inline-end

avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67
richard67 - comment - 23 Jan 2021

This can be done without any special LTR or RTL css

Use padding-inline-start and padding-inline-end

@brianteeman I know. But I was not sure regarding browser support. As I just can see we already use padding-inline at a few places. Will change it here, if that's wrong it has to be changed here and at these other places.

avatar richard67 richard67 - change - 23 Jan 2021
Labels Added: NPM Resource Changed ?
avatar richard67
richard67 - comment - 23 Jan 2021

@brianteeman Thanks, changed.

avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67 richard67 - change - 23 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 23 Jan 2021
avatar richard67
richard67 - comment - 23 Jan 2021

@brianteeman Unfortunately it seems that some other logical CSS properties which could be useful to fix the other issue with positioning of module edit buttons for RTL have less browser support: https://caniuse.com/?search=inset-inline-end . Can we use inset-inline now or should we better not to that (yet)?

avatar brianteeman
brianteeman - comment - 23 Jan 2021

Only when they have full browser support for the browsers that we support

avatar richard67
richard67 - comment - 23 Jan 2021

If I only knew which browsers we have to support ;-)

avatar brianteeman
brianteeman - comment - 23 Jan 2021

Not ie and all current browser versions and version minus 1

avatar richard67
richard67 - comment - 23 Jan 2021

As I can see we don't use inset-inline anywhere yet, in opposite to padding-inline and margin-inline, which both have better browser support than inset-inline.

avatar richard67 richard67 - change - 25 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 25 Jan 2021
avatar richard67 richard67 - change - 25 Jan 2021
The description was changed
avatar richard67 richard67 - edited - 25 Jan 2021
avatar chmst chmst - test_item - 25 Jan 2021 - Tested successfully
avatar chmst
chmst - comment - 25 Jan 2021

I have tested this item successfully on f30f5d5

Works as described.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32124.

avatar gostn gostn - test_item - 26 Jan 2021 - Tested successfully
avatar gostn
gostn - comment - 26 Jan 2021

I have tested this item successfully on f30f5d5


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32124.

avatar richard67 richard67 - change - 26 Jan 2021
Status Pending Ready to Commit
avatar richard67
richard67 - comment - 26 Jan 2021

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32124.

avatar drmenzelit drmenzelit - change - 26 Jan 2021
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2021-01-26 08:37:47
Closed_By drmenzelit
Labels Added: ?
avatar drmenzelit drmenzelit - close - 26 Jan 2021
avatar drmenzelit drmenzelit - merge - 26 Jan 2021
avatar drmenzelit
drmenzelit - comment - 26 Jan 2021

Thanks

avatar richard67
richard67 - comment - 26 Jan 2021

Thanks!

Add a Comment

Login with GitHub to post a comment