Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid xml namespaces on div elements #51

Closed
3 tasks done
benjaminkott opened this issue Apr 22, 2019 · 0 comments · Fixed by #52
Closed
3 tasks done

Invalid xml namespaces on div elements #51

benjaminkott opened this issue Apr 22, 2019 · 0 comments · Fixed by #52

Comments

@benjaminkott
Copy link
Member

Bug Report

Prerequisites

  • Can you reproduce the problem on TYPO3 v8.7 LTS
  • Can you reproduce the problem on TYPO3 v9.5 LTS
  • Did you perform a cursory search to see if your bug or feature is already reported?

Description

HTML Templates contain fluid namespace definitions on unsupported elements.

<div 
    xmlns:f="http://www.w3.org/1999/html" 
    xmlns:blog="http://typo3.org/ns/T3G/AgencyPack/Blog/ViewHelpers"
>
    ...
</div>

Steps to Reproduce

  1. Install Blog Extension
  2. Include Tempalte
  3. Insert "Blog: List of posts" plugin
  4. Check frontend markup

Expected behavior: [What you expected to happen]

Namespaces for fluid viewhelper resolving should not be rendered in frontend

Actual behavior: [What actually happened]

Invalid namespaces are rendered in the frontend.

Versions

All versions

benjaminkott added a commit that referenced this issue Apr 23, 2019
Fixes: #51
Releases: master, 9.1, 9.0, 8.7
benjaminkott added a commit that referenced this issue Apr 23, 2019
Fixes: #51
Releases: master, 9.1, 9.0, 8.7
benjaminkott added a commit that referenced this issue Apr 23, 2019
Fixes: #51
Releases: master, 9.1, 9.0, 8.7
benjaminkott added a commit that referenced this issue Apr 23, 2019
Fixes: #51
Releases: master, 9.1, 9.0, 8.7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant