fix: 🐛 Fix operator precedence in About customer URL href#57
Open
wapec wants to merge 1 commit into
Open
Conversation
The ternary and string concatenation were not grouped correctly — due to operator precedence, the expression evaluated as: condition ? 'http://' : urlCustomer instead of: (condition ? 'http://' : '') + urlCustomer When urlCustomer had no scheme, href became 'http://' with the actual URL silently dropped. Affects all white-labelled installations supplying customization.customer.www without a protocol prefix. Signed-off-by: Bohdan Baranov <wapec@icloud.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ternary and string concatenation were not grouped correctly — due to operator precedence, the expression evaluated as:
condition ? 'http://' : urlCustomer
instead of:
(condition ? 'http://' : '') + urlCustomer
When urlCustomer had no scheme, href became 'http://' with the actual URL silently dropped. Affects all white-labelled installations supplying customization.customer.www without a protocol prefix.
How to verify — logic level
Paste into any browser DevTools console:
Expected output:
example.comhttp://http://example.comexample.comhttp://http://example.comwww.example.comhttp://http://www.example.comhttps://example.comhttps://example.comhttps://example.comhttp://example.comhttp://example.comhttp://example.comHTTPS://example.comHTTPS://example.comHTTPS://example.comOnly inputs without an
http:///https://scheme expose the bug. Thelast three rows confirm the fix doesn't regress URLs that previously worked.
How to verify — UI
Open the mobile editor with
customization.customer.wwwset in the editorconfig. Navigate to Settings → About and inspect the customer URL link
(
#settings-about-url):The visible link text is identical in both builds — only
hrefdiffers,which is why the bug is easy to miss in casual visual review.
Screenshots (Pixel 5, dark theme)
example.comwww.example.comThe red/green banner overlay at the top of each screenshot shows the actual
hrefattribute on the rendered link — that's where the divergence lives.Test checklist
customer.www = "example.com"→ link href =http://example.com, click opens the sitecustomer.www = "www.example.com"→ link href =http://www.example.com, click opens the sitecustomer.www = "http://example.com"→ link href unchanged, click opens the sitecustomer.www = "https://example.com"→ link href unchanged, click opens the sitecustomer.www = "HTTPS://example.com"→ link href unchanged (case-insensitive)customer.wwwunset → link not rendered (existingurlCustomer?.lengthguard)