html - Responsvie website width -


When the width is coding for liability, is it better to round the price or to specify as much value as possible? For example:

Based on my calculations, my width is 67.328699% (left div) and 32.84% (right div)

or I only 67 <% P>

Two ways to focus on this Are there. First of all, due to the nature of the shooting point arithmetic, you are probably not getting an exact number, so the goal is not going to break anything. You are going to be absolutely right anyway. The clever people have written about this point:

Secondly, think of what the number really means 67.328699% is you trying to define the ten millionth element of one percent correctly, or In other words, its full screen width is hundred million. How much are you actually getting from doing this?

In addition, due to the boundaries of floating point math, it is possible that if you make the width 100% accurate, when the user changes the width of the screen or sometimes just with other offers, then you Division is going to be jumping. Sometimes they will be on the same line, sometimes they will not. I recommend that you add them to a little less than 100%.

EDIT: On the second note, I will discuss with your designer and ask why they have made such strange ratios that they should design around the technology, to force your job technique to fit into a design Do not have to.

Comments

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

java - JPA TypedQuery: Parameter value element did not match expected type -

c++ - static template member variable has internal linkage but is not defined -