Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9325

Closed
Open
Created May 23, 2015 by Administrator@rootOwner

Error while previewing Markdown of Milestone Edit.

Created by: praveenscience

  1. Summary: Markdown preview in the Edit Milestone doesn't work for https://gitlab.com/.

  2. Steps to reproduce:

    1. Go to your project, mine's a Private Project. (https://gitlab.com/username/project)
    2. Click on Milestones, existing one. (milestones) (milestones/1)
    3. Click on Edit. (milestones/1/edit)
    4. Click on Preview after writing any text.
  3. Expected behavior: Should show the preview after processing with GFM.

  4. Observed behavior: It throws an error:

    Uncaught Error: Syntax error, unrecognized expression: .zennable input[type=checkbox]##md-preview-holder.
  5. Relevant logs and/or screenshots:

    gitlab

  6. Output of checks: This is in the production version of the GitLab, and the bug is present at the time of posting this issue.

  7. Possible fixes: Looks like a JavaScript DOM query error, and since the code is minified, I am not able to find the exact solution.

Assignee
Assign to
Time tracking