Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,994
    • Issues 36,994
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,449
    • Merge requests 1,449
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #20099

Closed
Open
Created Nov 08, 2017 by dmoonfire@dmoonfire

Markdown with YAML rendering doesn't handle UTF8 BOM

Summary

If you check in Markdown file with a UTF-8 BOM marker, it does not render a YAML header as a code block.

Steps to reproduce

  1. Create a Markdown file with a YAML header
  2. Make sure it has a BOM (using Notepad++ for example)
  3. Check it in
  4. Preview it

Example Project

https://gitlab.com/dmoonfire/gitlab-markdown-bom

What is the current bug behavior?

The BOM causes it not to correctly identify the YAML header and format at it.

What is the expected correct behavior?

It would treat files with and without BOM identically.

Relevant logs and/or screenshots

With BOM:

image

Without BOM:

image

Output of checks

This bug happens on GitLab.com.

Possible fixes

Sorry.

Assignee
Assign to
13.6
Milestone
13.6 (Past due)
Assign milestone
Time tracking