Skip to content

refactor: remove <style> section and use bootstrap class instead#722

Merged
tblivet merged 2 commits intoPrestaShop:developfrom
bibips:remove-useless-style
Sep 9, 2025
Merged

refactor: remove <style> section and use bootstrap class instead#722
tblivet merged 2 commits intoPrestaShop:developfrom
bibips:remove-useless-style

Conversation

@bibips
Copy link
Contributor

@bibips bibips commented Jun 19, 2025

Questions Answers
Description? Remove <style> section and use bootstrap class instead (in compliance with the BEM convention)
Type? refactor
BC breaks? no
Deprecations? no
Fixed ticket? Fixes #721
Sponsor company
How to test? Go to Contact page and check whether the URL input field is still hidden.

@ps-jarvis
Copy link

Hello @bibips!

This is your first pull request on hummingbird repository of the PrestaShop project.

Thank you, and welcome to this Open Source community!

@github-project-automation github-project-automation bot moved this to Ready for review in PR Dashboard Jun 19, 2025
Copy link

@aomaxime aomaxime left a comment

Choose a reason for hiding this comment

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

Ok for me

@Hlavtox
Copy link
Contributor

Hlavtox commented Aug 8, 2025

Just to check - Why is the form input hidden? Is it always?

If not, are we sure the related js triggers class or style?
If yes, wouldn't an input type=hidden be better?

@bibips
Copy link
Contributor Author

bibips commented Aug 8, 2025

Just to check - Why is the form input hidden? Is it always?

If not, are we sure the related js triggers class or style? If yes, wouldn't an input type=hidden be better?

If I'm not wrong it a protection against spam. The only purpose of url input is to be empty and alway hidden.
PrestaShop/contactform@7800cec
{3CEDA980-4185-4E97-9406-D87082E4D258}

I think that this input is type="text" because some bot doesn't fill hidden input.
It's a feature that was introduced in 2018, so I'm not sure if it's still useful because bots are smarter now.

@Hlavtox What do you think? Is it an obsolete way of preventing spam, so that we can set the input to type="hidden", or do we need to keep it as type="text"?

@Hlavtox
Copy link
Contributor

Hlavtox commented Aug 8, 2025

@tblivet @ga-devfront Guys, any idea why it was there? Maybe there will be some evidence in git blame of classic theme.

@tblivet
Copy link
Contributor

tblivet commented Aug 8, 2025

Hi @Hlavtox, this was already fixed but on the improvement branch : 64280d2

@bibips bibips force-pushed the remove-useless-style branch from f7383c1 to 6c41c2b Compare August 8, 2025 18:03
@ps-jarvis
Copy link

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

  • Shop.Theme.Customeraccount
    • Tracking

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

@bibips
Copy link
Contributor Author

bibips commented Aug 8, 2025

Thank you, @tblivet. I updated the PR.

@bibips
Copy link
Contributor Author

bibips commented Aug 11, 2025

The waiting for wording label is incorrect... no translation string was added with this branch.
Could someone please remove this label ?

@ps-jarvis ps-jarvis moved this from Ready for review to To be tested in PR Dashboard Aug 26, 2025
@paulnoelcholot paulnoelcholot self-assigned this Aug 27, 2025
Copy link

@paulnoelcholot paulnoelcholot left a comment

Choose a reason for hiding this comment

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

Hello @bibips,

I tested your PR and it's good for me!

Thanks!

@tblivet tblivet merged commit efac429 into PrestaShop:develop Sep 9, 2025
6 checks passed
@github-project-automation github-project-automation bot moved this from To be tested to Merged in PR Dashboard Sep 9, 2025
@ps-jarvis ps-jarvis moved this from Merged to To be tested in PR Dashboard Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

A <style> node is present in the middle of a template.

6 participants