Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M MathJax
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 304
    • Issues 304
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MathJax
  • MathJax
  • Issues
  • #2859
Closed
Open
Issue created Apr 04, 2022 by Peter Krautzberger@pkraContributor

[SVG] consider setting stroke-width to 0

https://github.com/mathjax/MathJax-src/blob/2dd53ce6c8af3c9cceba0baf014ea9b065130774/ts/output/svg/Wrappers/TextNode.ts#L49-L53

sets the stroke-width to 3. This leads to weird rendering in edge cases (e.g. using print-to-PDF the output will look extremely bold in most PDF readers even if it will print fine).

I recall we discussed this for v2 ages ago and I think the original reason was to cover for flaky SVG rendering in old browser engines.

We've been using 0 in production for years now (in v2) and I just noticed that I had missed this declaration when we switched to v3 last year.

Running a small random sample through visual regression testing, it looks like switching to 0 can affect some stretchy constructions (for the better - they come out a hair thinner especially which improves where they connect with non-stretchy pieces). I didn't test ancient or dead browser engines but I used to test down to IE9 so I'm relatively certain this won't cause significant problems.

Assignee
Assign to
Time tracking