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

Responsive visual issues new product page #35775

Conversation

mattgoud
Copy link
Contributor

@mattgoud mattgoud commented Mar 28, 2024

Questions Answers
Branch? 8.1.x
Description? see #32218
Type? bug fix
Category? BO
BC breaks? no
Deprecations? no
How to test? go to product page and test each tab (fork : https://github.com/mattgoud/PrestaShop/tree/fix/32218-responsive-visual-issues-new-product-page)
UI Tests https://github.com/florine2623/testing_pr/actions/runs/8797116451
Fixed issue or discussion? Fixes #32218 & #36097 (with the exception of point number 4 : creation of a separate issue see #35765
Related PRs If theme, autoupgrade or other module change is needed to make this change work, provide a link to related PRs here.
Sponsor company Your company or customer's name goes here (if applicable).

@mattgoud mattgoud requested a review from a team as a code owner March 28, 2024 15:53
@prestonBot
Copy link
Collaborator

Hello @mattgoud!

This is your first pull request on the PrestaShop project. Thank you, and welcome to this Open Source community!

@prestonBot
Copy link
Collaborator

Hi, thanks for this contribution!

I found some issues with the Pull Request description:

  • Your pull request does not seem to fix any issue, consider creating one (see note below) and linking it by writing Fixes #1234.

Would you mind having a look at it? This will help us understand how interesting your contribution is, thank you very much!

About linked issues

Please consider opening an issue before submitting a Pull Request:

  • If it's a bug fix, it helps maintainers verify that the bug is effectively due to a defect in the code, and that it hasn't been fixed already.
  • It can help trigger a discussion about the best implementation path before a single line of code is written.
  • It may lead the Core Product team to mark that issue as a priority, further attracting the maintainers' attention.

(Note: this is an automated message, but answering it will reach a real human)

@prestonBot prestonBot added 8.1.x Branch Bug fix Type: Bug fix labels Mar 28, 2024
@mattgoud mattgoud force-pushed the fix/32218-responsive-visual-issues-new-product-page branch from 6d35420 to 8f41bd1 Compare March 28, 2024 16:29
Comment on lines 482 to 484
.material-icons {
margin-top: 0;
}
Copy link
Contributor

@SharakPL SharakPL Mar 28, 2024

Choose a reason for hiding this comment

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

I really doubt this requires a selector made of 6 components, including 2 IDs 😱
obraz

Did you try adding mt-0 class to that element?

I'm guessing it's not that easy since it's probably nested in some twig partial used in many places, but surely it can be shortened to 2-3 components selector to be specific enough.

Copy link
Contributor

Choose a reason for hiding this comment

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

I would go for utility classes where we can, maybe not the most performant solution, but it's much safer making changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hello, ok this is a somewhat specific need (on a single go-to-catalog button). I have reduced the depth of the classes nesting if you prefer.

@jolelievre jolelievre linked an issue Apr 9, 2024 that may be closed by this pull request
2 tasks
jolelievre
jolelievre previously approved these changes Apr 9, 2024
Copy link
Contributor

@jolelievre jolelievre left a comment

Choose a reason for hiding this comment

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

Thanks @mattgoud

boherm
boherm previously approved these changes Apr 9, 2024
@mattgoud mattgoud force-pushed the fix/32218-responsive-visual-issues-new-product-page branch 2 times, most recently from 12ae5e2 to 5c10baf Compare April 26, 2024 11:54
@MatShir
Copy link
Contributor

MatShir commented Apr 26, 2024

I was talking of the number 9 🙄

@MatShir MatShir removed Waiting for author Status: action required, waiting for author feedback Waiting for QA Status: action required, waiting for test feedback labels Apr 26, 2024
@mattgoud
Copy link
Contributor Author

I was talking of the number 9 🙄

ok thank you for your feedbacks @MatShir @Hlavtox , yes on mobile it will be a native select. @florine2623 I will only deal with number 3

@ps-jarvis ps-jarvis added the Waiting for QA Status: action required, waiting for test feedback label May 13, 2024
@paulnoelcholot
Copy link

Hello @mattgoud,

I tested your PR and I found this :
image
But on mobile I found this :
image

This bug can't be corrected on mobile? 🤔

Thanks for your feedback

@paulnoelcholot paulnoelcholot added the Waiting for author Status: action required, waiting for author feedback label May 27, 2024
@Hlavtox
Copy link
Contributor

Hlavtox commented May 27, 2024

@paulnoelcholot What is wrong with the second image?

@paulnoelcholot
Copy link

@Hlavtox, is this the expected behavior? 🤔

@Hlavtox
Copy link
Contributor

Hlavtox commented May 27, 2024

@paulnoelcholot It looks how it should. 👍

@paulnoelcholot
Copy link

My apologize!

So it's good for me!

Thanks!

@paulnoelcholot paulnoelcholot removed Waiting for author Status: action required, waiting for author feedback Waiting for QA Status: action required, waiting for test feedback labels May 27, 2024
@ps-jarvis ps-jarvis added the Waiting for QA Status: action required, waiting for test feedback label May 27, 2024
@paulnoelcholot paulnoelcholot added QA ✔️ Status: check done, code approved and removed Waiting for QA Status: action required, waiting for test feedback labels May 27, 2024
@prestonBot
Copy link
Collaborator

QA approved, well done! Message to the maintainers: do not forget to milestone it before the merge.

@nicosomb nicosomb merged commit dec2a9e into PrestaShop:8.1.x May 27, 2024
38 checks passed
@nicosomb nicosomb added this to the 8.1.7 milestone May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.1.x Branch Bug fix Type: Bug fix QA ✔️ Status: check done, code approved
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Visual issues on the new product page (mobile)