Kaynağa Gözat

Fix inappropriate markdown post process end tag check

When <code> is nested inside <pre>, the next end tag token would not able to be the same
as outer-most start tag. So we only check outer-most start and end tag token to be the same.
Unknwon 9 yıl önce
ebeveyn
işleme
341da3cea7
4 değiştirilmiş dosya ile 5 ekleme ve 5 silme
  1. 1 1
      README.md
  2. 1 1
      gogs.go
  3. 2 2
      modules/base/markdown.go
  4. 1 1
      templates/.VERSION

+ 1 - 1
README.md

@@ -3,7 +3,7 @@ Gogs - Go Git Service [![Build Status](https://travis-ci.org/gogits/gogs.svg?bra
 
 ![](https://github.com/gogits/gogs/blob/master/public/img/gogs-large-resize.png?raw=true)
 
-##### Current version: 0.8.38
+##### Current version: 0.8.39
 
 | Web | UI  | Preview  |
 |:-------------:|:-------:|:-------:|

+ 1 - 1
gogs.go

@@ -17,7 +17,7 @@ import (
 	"github.com/gogits/gogs/modules/setting"
 )
 
-const APP_VER = "0.8.38.0217"
+const APP_VER = "0.8.39.0219"
 
 func init() {
 	runtime.GOMAXPROCS(runtime.NumCPU())

+ 2 - 2
modules/base/markdown.go

@@ -303,10 +303,10 @@ OUTER_LOOP:
 					}
 
 					// If this is the close tag to the outer-most, we are done
-					if token.Type == html.EndTagToken && strings.EqualFold(tagName, token.Data) {
+					if token.Type == html.EndTagToken {
 						stackNum--
 
-						if stackNum == 0 {
+						if stackNum <= 0 && strings.EqualFold(tagName, token.Data) {
 							break
 						}
 					}

+ 1 - 1
templates/.VERSION

@@ -1 +1 @@
-0.8.38.0217
+0.8.39.0219