Skip to content

Conversation

@openorclose
Copy link
Contributor

What is the purpose of this pull request? (put "X" next to an item, remove the rest)

• [x] Bug fix

What is the rationale for this request?

Fixes #1154

What changes did you make? (Give an overview)

Specifically called the componentParser on the popovers in the footnotes plugin

Provide some example code that this change will affect:

**Normal footnotes:**
Here is a footnote reference,[^1] and another.[^longnote][^1]: Here is the footnote. Footnotes will appear at the bottom of the page.
​
[^longnote]: Here's one with multiple blocks.
​
    Subsequent paragraphs are indented to show that they
belong to the previous footnote.


**Inline footnotes:**
Here is an inline note.^[Inlines notes are easier to write, since
you don't have to pick an identifier and move down to type the
note.]

Is there anything you'd like reviewers to focus on?

This is the simple bug fix for now. Long term solution to fix footnotes inside dynamic panels is still in the works.

Testing instructions:

Check that the popovers appear.

Proposed commit message: (wrap lines at 72 characters)

During the migration to bootstrap-vue, popovers had to be parsed into bootstrap-vue syntax.

This is done before the plugins stage, where footnotes are implemented, so the popovers don't work there.

Let's add the parsing of popovers to the footnotes plugin to solve this.

During the migration to bootstrap-vue,
popovers had to be parsed into bootstrap-vue syntax.

This is done before the plugins stage, where footnotes are implemented, so the popovers don't work there.

Let's add the parsing of popovers to the footnotes plugin to solve this.
@le0tan le0tan added c.Bug 🐛 p.Medium pr.BugFix 🐛 Fixes correct a programming error/assumption and removed c.Bug 🐛 p.Medium labels Mar 29, 2020
you don't have to pick an identifier and move down to type the
note.</p>
</div>
</span>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weird that the indents are incorrect, but i assume this is what updatetest generated, so can't really argue with this, can I?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah..

Copy link
Contributor

@ang-zeyu ang-zeyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

@ang-zeyu ang-zeyu added this to the v2.13.2 milestone Apr 2, 2020
@yamgent
Copy link
Member

yamgent commented Apr 5, 2020

@openorclose resolve conflicts

…vers

# Conflicts:
#	test/functional/test_site/expected/index.html
@openorclose
Copy link
Contributor Author

@openorclose resolve conflicts

Done!

@yamgent yamgent merged commit 9984374 into MarkBind:master Apr 7, 2020
Tejas2805 added a commit to Tejas2805/markbind that referenced this pull request Apr 9, 2020
* 'master' of https://github.com/MarkBind/markbind: (41 commits)
  Document adding new site content in DG (MarkBind#1153)
  Add relative date feature (MarkBind#908)
  Use <br> to separate lines of code block (MarkBind#1176)
  Parse popovers for footnotes (MarkBind#1155)
  Resolve comments
  Expand test extensions and fix whitespace checks (MarkBind#1156)
  Address comments
  Upgrade js-beautify and provide option to turn it off (MarkBind#1116)
  Normalize inline puml line ending before hashing (MarkBind#1174)
  Update tests (MarkBind#1178)
  Remove fixed bugs from test\functional\test_site\bugs\index.md` (MarkBind#1148)
  Fix bug in Search for UG and DG (MarkBind#1147)
  Add inline puml support (MarkBind#1100)
  Fix hrefs for headings with angular brackets (MarkBind#1089)
  Update tests for 2.13.1 (MarkBind#1169)
  2.13.1
  Update vue-strap version to v2.0.1-markbind.39
  Fix fontawsome icons don't show underlines to indicate modal/tooltip (MarkBind#1133)
  2.13.0
  Update test files
  ...
marvinchin pushed a commit that referenced this pull request Apr 10, 2020
During the migration to bootstrap-vue,
popovers had to be parsed into bootstrap-vue syntax.

This is done before the plugins stage, where footnotes are implemented, so the popovers don't work there.

Let's add the parsing of popovers to the footnotes plugin to solve this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr.BugFix 🐛 Fixes correct a programming error/assumption

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Footnotes don't show popovers

5 participants