fix(webserver): remove stray leading brace in style.css and normalize formatting - #78
Merged
ngosang merged 1 commit intoJun 11, 2026
Conversation
… formatting style.css started with an orphan closing brace on line 1, a remnant of a selector lost at some point. It is a CSS parse error: browsers recover by skipping it, so rendering was not affected, but it is a trap for future edits and trips up validators and tooling. Remove the stray brace and normalize the formatting of the file (tab indentation, consistent "property: value;" spacing) without changing any selector or declaration, so the rendered result is identical. Verified against a running amuleweb: the served style.css matches, parses with balanced braces, and the pages render unchanged.
ngosang
changed the title
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
1 participant
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.
style.css started with an orphan closing brace on line 1, a remnant of a selector lost at some point. It is a CSS parse error: browsers recover by skipping it, so rendering was not affected, but it is a trap for future edits and trips up validators and tooling.
Remove the stray brace and normalize the formatting of the file (tab indentation, consistent "property: value;" spacing) without changing any selector or declaration, so the rendered result is identical.
Verified against a running amuleweb: the served style.css matches, parses with balanced braces, and the pages render unchanged.