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

www/nginx: 1.33 #3678

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

www/nginx: 1.33 #3678

wants to merge 21 commits into from

Conversation

kulikov-a
Copy link
Member

@kulikov-a kulikov-a commented Nov 18, 2023

Hi!
a few more suggestions )

Thanks!
image

@fichtner fichtner self-assigned this Nov 20, 2023
@fichtner fichtner requested review from fichtner, 8191 and fabianfrz and removed request for fichtner November 20, 2023 10:28
Copy link
Member

@fabianfrz fabianfrz left a comment

Choose a reason for hiding this comment

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

looks almost good

Co-Authored-By: Fabian Franz BSc <fabianfrz@users.noreply.github.com>
@kulikov-a
Copy link
Member Author

kulikov-a commented Dec 15, 2023

@fabianfrz i removed .filter-option css rule (introduced in 1.32) to reflect core selectpicker update.
image
image

Copy link
Member

@fabianfrz fabianfrz left a comment

Choose a reason for hiding this comment

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

reviewed again - looks already good - a few minor things.

Co-Authored-By: Fabian Franz BSc <fabianfrz@users.noreply.github.com>
@kulikov-a kulikov-a marked this pull request as draft December 23, 2023 06:04
@kulikov-a
Copy link
Member Author

kulikov-a commented Dec 23, 2023

@fabianfrz Thanks for the review! I'll try to take your suggestions asap.
Sorry, I didn’t understand one thing: what do you mean by the need for translation in dialogues?
upd. or you mean to translate '{{ lang._('Ok') }}' ? 😃 (I'll proceed from this and update everything tomorrow)

Co-authored-by: Fabian Franz BSc <fabianfrz@users.noreply.github.com>
@fabianfrz
Copy link
Member

@kulikov-a yes, the label, the rest looks translated.

kulikov-a and others added 3 commits December 24, 2023 09:16
Co-Authored-By: Fabian Franz BSc <fabianfrz@users.noreply.github.com>
-don't use global vars unnecessarily
-move css to separate file
-don't touch DOM for clipboard copy. use stored value
-don't use <pre> if violating standard
-add Button label translation
-check if clipboard write supported before link show()
-use text() instead of html() if possible
-change 'DOM ready' handler syntax
thnx @fabianfrz
@kulikov-a
Copy link
Member Author

@fabianfrz can you look one more time please )
hope I fixed everything.
I chose the first variant of DOM-ready handler because I didn’t find such syntax in core code and I would like to follow the core style (I'll be happy to switch to ES6 as soon as I see this in core)
same with the buttons - imho they are now where the user expects to see them, given the style of other pages.
XSS possibility discussion: #3678 (comment)
thanks!

@kulikov-a kulikov-a marked this pull request as ready for review December 24, 2023 08:43
use lodash _.unescape to safely decode string without DOM manipulations
@fabianfrz
Copy link
Member

@kulikov-a regarding ES6: The core was longer supporting IE than my plugins, because they never did (the nginx plugin was on ES6 since day one). So the core was always slower in adopting the new JavaScript syntax. Nowadays you can use ES6 features in core as well since IE is dead.

@kulikov-a
Copy link
Member Author

@fabianfrz Thanks!
I'll be happy to try using ES6 even for DOM-ready event on next PRs.
Just trying to follow the product code style (waiting for such a notation to appear in the core or permission from @fichtner and @AdSchellevis)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants