Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AC-8699] Magento Pages Width does not match anymore for Long width c… #37476

Open
wants to merge 14 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

adamphh
Copy link
Contributor

@adamphh adamphh commented May 9, 2023

[AC-8699] Magento Pages Width does not match anymore for Long width content after 2.4.6 upgrade #37459

Description (*)

Preconditions and environment

Magento version 2.4.6

Steps to reproduce

  1. Navigate Product Grid
  2. Add atleast 10 more column visible from columns dropdown.
    3.Scroll down till last content and then scroll right. You will see the page width did not match columns width.

Expected result

While adding more columns in any grid should match full page width. Issue was not there in 2.4.5

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Magento Pages Width does not match anymore for Long width content after 2.4.6 upgrade #37459

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented May 9, 2023

Hi @adamphh. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:
  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: pending review labels May 9, 2023
@@ -9,6 +9,7 @@

.catalog-product-index {
.admin__data-grid-wrap {
overflow-x: scroll;
.data-row {
Copy link
Contributor

Choose a reason for hiding this comment

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

in myopinion properties should overflow-x: auto instead always show scroll

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mrtuvn Thanks for your response. Yes, I think it should be auto instead of scroll. I already updated it.

Copy link
Member

Choose a reason for hiding this comment

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

@adamphh This commit only fixes product grid but this issue is happening for all the magento backend ui-grids.
@mrtuvn

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@irajneeshgupta Thanks for your comment. I will resolve it

Copy link
Contributor

@mrtuvn mrtuvn 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 to me

@mrtuvn
Copy link
Contributor

mrtuvn commented May 10, 2023

weird things i can't find/encounter this issue happen in version 2.3.7 ? Any code update after that ?

@mrtuvn
Copy link
Contributor

mrtuvn commented May 10, 2023

evid

@mrtuvn
Copy link
Contributor

mrtuvn commented May 10, 2023

Seem this changes in this commit make regression issue
ba93336

@mrtuvn
Copy link
Contributor

mrtuvn commented May 10, 2023

Hi Can you check my last comment

adamphh added 2 commits May 11, 2023 00:02
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…ontent after 2.4.6 upgrade magento#37459

Update code to resolve make regression issue #ba93336
@adamphh
Copy link
Contributor Author

adamphh commented May 11, 2023

Hi Can you check my last comment

@mrtuvn I push the new modification. Please help to check it again

@@ -429,7 +430,7 @@ body._in-resize {
.data-grid-actions-cell {
padding-left: @data-grid-cell__padding-horizontal * 2;
padding-right: @data-grid-cell__padding-horizontal * 2;
position: relative;
position: inherit;
text-align: center;
Copy link
Contributor

Choose a reason for hiding this comment

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

any reason of this update position

Copy link
Contributor

Choose a reason for hiding this comment

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

can it's work without it ?

Copy link
Contributor

Choose a reason for hiding this comment

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

hi @adamphh can you explain more about this changes

Copy link
Contributor

Choose a reason for hiding this comment

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

If no specific or special reason i suggest to remove for reduce extra css property

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mrtuvn there is no special reason for that, it can work without position, However I am not sure if it affect to another section.

adamphh added 3 commits May 12, 2023 00:17
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
@mrtuvn mrtuvn requested a review from irajneeshgupta May 17, 2023 00:07
Copy link
Contributor

@mrtuvn mrtuvn left a comment

Choose a reason for hiding this comment

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

can you check my last response

adamphh added 2 commits May 19, 2023 05:12
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
adamphh added 4 commits May 26, 2023 11:23
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
…oes_not_match_anymore_for_long_width_content_after_2.4.6_upgrade_37459
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Admin UI Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: review
Projects
Status: Review in Progress
Development

Successfully merging this pull request may close these issues.

Magento Pages Width does not match anymore for Long width content after 2.4.6 upgrade
3 participants