Mpdf css display issues - print vs screen
The mpdf specifications state that the display settings inline or block can not be changed.
I am trying to export a PDF that has a css-styled tooltip popping up on screen, but it should be invisible in the PDF.
The printed version is perfect, the on screen version too, only the PDF is wrong.
The following html/css will output the tooltip inline (as if it were part of the text) on the PDF (I want to keep it invisible):
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
The css:
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
This shows the tooltiptext on hovering (screen) or keeps it invisible(print), but shows it inline on the pdf:
blah hover this to see tooltiptext this information pops up on overing over the previous words defined in the tooltip class blahblah.
Mpdf does not apply the styling of the span items.
Changing the spans to divs with display inline has the same result on screen and print, but the PDF will show the divs as blocks (with "linebreaks" mid-sentence). It does not take the display:inline styling (according to the mpdf specs):
blah
hover this to see tooltiptext
blahblah.
I can not seem to find a solution to my problem. Anyone any ideas on how to do this?
html css mpdf
add a comment |
The mpdf specifications state that the display settings inline or block can not be changed.
I am trying to export a PDF that has a css-styled tooltip popping up on screen, but it should be invisible in the PDF.
The printed version is perfect, the on screen version too, only the PDF is wrong.
The following html/css will output the tooltip inline (as if it were part of the text) on the PDF (I want to keep it invisible):
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
The css:
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
This shows the tooltiptext on hovering (screen) or keeps it invisible(print), but shows it inline on the pdf:
blah hover this to see tooltiptext this information pops up on overing over the previous words defined in the tooltip class blahblah.
Mpdf does not apply the styling of the span items.
Changing the spans to divs with display inline has the same result on screen and print, but the PDF will show the divs as blocks (with "linebreaks" mid-sentence). It does not take the display:inline styling (according to the mpdf specs):
blah
hover this to see tooltiptext
blahblah.
I can not seem to find a solution to my problem. Anyone any ideas on how to do this?
html css mpdf
add a comment |
The mpdf specifications state that the display settings inline or block can not be changed.
I am trying to export a PDF that has a css-styled tooltip popping up on screen, but it should be invisible in the PDF.
The printed version is perfect, the on screen version too, only the PDF is wrong.
The following html/css will output the tooltip inline (as if it were part of the text) on the PDF (I want to keep it invisible):
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
The css:
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
This shows the tooltiptext on hovering (screen) or keeps it invisible(print), but shows it inline on the pdf:
blah hover this to see tooltiptext this information pops up on overing over the previous words defined in the tooltip class blahblah.
Mpdf does not apply the styling of the span items.
Changing the spans to divs with display inline has the same result on screen and print, but the PDF will show the divs as blocks (with "linebreaks" mid-sentence). It does not take the display:inline styling (according to the mpdf specs):
blah
hover this to see tooltiptext
blahblah.
I can not seem to find a solution to my problem. Anyone any ideas on how to do this?
html css mpdf
The mpdf specifications state that the display settings inline or block can not be changed.
I am trying to export a PDF that has a css-styled tooltip popping up on screen, but it should be invisible in the PDF.
The printed version is perfect, the on screen version too, only the PDF is wrong.
The following html/css will output the tooltip inline (as if it were part of the text) on the PDF (I want to keep it invisible):
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
The css:
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
This shows the tooltiptext on hovering (screen) or keeps it invisible(print), but shows it inline on the pdf:
blah hover this to see tooltiptext this information pops up on overing over the previous words defined in the tooltip class blahblah.
Mpdf does not apply the styling of the span items.
Changing the spans to divs with display inline has the same result on screen and print, but the PDF will show the divs as blocks (with "linebreaks" mid-sentence). It does not take the display:inline styling (according to the mpdf specs):
blah
hover this to see tooltiptext
blahblah.
I can not seem to find a solution to my problem. Anyone any ideas on how to do this?
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
.tooltip .tooltiptext {
visibility: hidden;
position: absolute;
z-index: 1;}
.tooltip:hover .tooltiptext {visibility: visible;}
@media print {
.tooltip .tooltiptext,.tooltip:hover .tooltiptext { visibility: hidden; display:none;}
}
<p>blah <span class="tooltip">hover this to see tooltiptext<div class="tooltiptext"> this information pops up on hovering over the previous words defined in the tooltip class</span> </span> blahblah.</p>
html css mpdf
html css mpdf
asked Nov 26 '18 at 9:52
bolvobolvo
111111
111111
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53478509%2fmpdf-css-display-issues-print-vs-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53478509%2fmpdf-css-display-issues-print-vs-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown