dompdf / dompdf/dompdf

script blocks in document header are not processed

Open
#398 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug imported Priority-Medium
Dominant language
PHP
Stars
11.2k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

Original author: OneWinge...@gmail.com (December 15, 2011 00:25:19)

What steps will reproduce the problem?

  1. Pass the inner-HTML of the body of an HTML document with a <script type=text/php> tag inside it; or, alternatively, with the script inside the head-section (http://www.w3schools.com/tags/tag_head.asp).
  2. Pass the above to render.

What is the expected output? What do you see instead?
Expected the script, in this case a header as per FAQ examples, to execute and draw the header; results: PDF produced as normal, but w/o the script executing.

What version of the product are you using? On what operating system?
OS: Linux 2.6.35.14-96.fc14.i686 / GNOME 2.32.0
DOMPDF: 0.6.0 beta2

Please provide the HTML source code you want to convert, or any additional
information.

Original issue: http://code.google.com/p/dompdf/issues/detail?id=392

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the render entry point described in the reproduction and trace how script tags are handled in the document head versus the body. Use the supplied text/php header example to verify that the script executes and draws the header in the generated PDF.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.