Copy link to clipboard
Copied
when I create a table, I add column to have vertical line dividers. I assign them to be 1 pt wide. Coding shows them as 1 pt wide. However when viewed browser, they appear wider than 1 pt. What am I doing wrong. How can I fix?
example code:
<td width="1" bgcolor="#FF9900"> </td> -- this is what I want as a think line divider. But shows wider than 1pt. Thanks for any help!!
<table width="550" border="0">
<tr>
<td colspan="4"><hr></td>
</tr>
<tr>
<td width="164"><a href="http://corp.abc.com"><img name="" src="https://www.thinkedu.com/images/thinkEDU-logo_tag_noncom_150.jpg" width="150" height="61" alt="ThinkEDU Logo"></a></td>
<td width="1" bgcolor="#FF9900"> </td>
<td width="9" valign="top"><br></td>
<td width="358" valign="top"><font size="1" color="000000" face="Verdana, Arial, Helvetica, sans-serif"><strong>Allan David | Chief Operating Officer</strong><br>
ABC, LLC | www.xyz.com<br>
</font></td>
</tr>
</table>
1pt = 1.33333333333px
Having said that, eachbrowser has default settings of its own. Sometimes they may be the same across browsers, sometimes they differ. For that reason, many developers use a so called CSS reset.
To illustrate the default setting of the browser for a table cell, add the following style rules to your document.
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Untitled Document</title>
<style>
td {
margin: 0;
padding: 0;
}
</style>
</head>
Copy link to clipboard
Copied
1pt = 1.33333333333px
Having said that, eachbrowser has default settings of its own. Sometimes they may be the same across browsers, sometimes they differ. For that reason, many developers use a so called CSS reset.
To illustrate the default setting of the browser for a table cell, add the following style rules to your document.
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Untitled Document</title>
<style>
td {
margin: 0;
padding: 0;
}
</style>
</head>
Copy link to clipboard
Copied
Hello Ben,
could you detail the report that you install between the relation pixel / point on the one hand and the reinitialization of the defaults of properties css on the other hand.
Copy link to clipboard
Copied
px to Point Converter, Chart -- EndMemo
Copy link to clipboard
Copied
thanks Ben, in fact I know the relation in between the point an the pixel, and the retina aspect of it...
the question was waht is the relationship in between this previous finding and the fact of pointing to a reset CSS... what is the relation in between (px/pt) and reset CSS ?
Copy link to clipboard
Copied
Because I don't use points, preferring to use pixels, ems and rems in my design, I thought that the OP could be referring to px instead of pt. My bad for which I apologise.
As far as the CSS reset is concerned, it .... anyhow, you know about that as well.
Copy link to clipboard
Copied
well don't you use pt for css print ?
Copy link to clipboard
Copied
I do not have a separate CSS for print. If I include a report to be printed out, then I convert this to a PDF which leans itself more to printing than HTML
As an example, after filling out all of the details in the various tabs as in
how great is a hard copy
This could never be achieved by printing an HTML document.
Copy link to clipboard
Copied
The example brings tears in my eyes when I consider that I chose the Spry framework together with ADDT to create the site. Not responsive is the only complaint.
Copy link to clipboard
Copied
I don't understand what couldn't be printed that way using CSS ??
anyway when converting to PDF you will have to also convert the display rendering... so what be done using PDF engine could also be done using CSS rendering don't you think ?
FWIT when one is using a PDF workflow is because one need to dematerialize the content and distribute it on that format... when someone print a document it is generally because this person need to get the content on a paper sheet... and that's why CSS print can be usefull... don't you think ?
(above are just questions, to share and exchange point of view, not argue)
Copy link to clipboard
Copied
I think that it depends on whether the articles are to be viewed and used mainly on screen or mainly as a hardcopy.
In my case, I have assumed that the sites that I have created are to be viewed on screen and as such I have made no effort to include a print CSS. But yes, I do concede that there are instances that a printable copy of the page be made available and in such a case I would provide a print CSS. The extent to which I would go is to hide certain sections (like the menubar) of the page.
Copy link to clipboard
Copied
Hey, you are keeping me from watching the Australian Open tennis.
Copy link to clipboard
Copied
I've got for you the replay of the last final set...
Copy link to clipboard
Copied
That is funny as. I had to share it with my family and they all love you.
Copy link to clipboard
Copied
well if you liked the flat version, you will probably love the almost 3d version... (either if still flat)
Copy link to clipboard
Copied
yes that it is completly a way... printing process should also FWIT think in grayscale, because most of the printer out there (government, hospital, office...) just run black and white printer and colors don't always render nice in such a convertion...
usualy background are removed by default... but having them strongly CSS handled can be a real plus to give some reading contrast too...
but back to the initial point I think that using PT instead of PT, and having a responsive attitude depending on the paper that the user will print can be a real plus...