We’ve released the first version of jQDynamicFontSize – a jQuery Plugin for dynamically adjusting the font size of an element to fit a number of lines. The plugin was written to allow us to resize a headline to make the headline fit on one line, sacrificing text size to avoid breaking text into two lines.
To paraphrase from the INSTALL file:
In a production system, use jquery-dynamicfontsize.min.js. For debugging
or developing, use jquery-dynamicfontsize.js.
Include a reference to the script after loading jQuery:
This will attempt to scale the font size of the element down with 10% in
3 iterations, stopping when a value has been found that allows the element
to only use one text line.
This will attempt to scale all h1 elements. Other jQuery selectors will also
* squeezeFactor: A float value that will be used as the squeeze factor
for each step. 0.1 means that we'll attempt to scale the font-size down
10% for each iteration. Defaults to 0.1.
* lines: The number of lines we'll attempt to fit the text to. When the
text fits this (or a smaller) amount of lines, we'll stop scaling.
Defaults to 1.
* tries: The number of iterations we'll try before we give up and go with
the last result. Defaults to 3.
I investigated a strange problem yesterday, where the back button in Firefox returned the user to the top of the previous page, instead of to the location where he already had scrolled. The problem seemed to have brought its fair share of problems for developers all over, and a thread detailing the problem in Drupal provided the information needed to solve it. The problem is actually so wide-spread that there is a dedicated Firefox extension to solve the issue (Restore Scroll Position).
Anyways, the issue stems from the Cache-Control headers that PHP among others include by default:
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
The problem is that the “no-store” directive tells the browser do NOT store a version of the page anywhere, not temporarily, not .. ever. Internet Explorer and Opera still remembers the position, but Firefox decided to take everything a step further and does not keep any information available. The extension mentioned above saves the scroll position in another location and then restores the scroll position after navigating back to the page.
The problem is solved by changing the Cache-Control header:
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
A very helpful tip here is that you probably need to restart Firefox to make it respect the new header, as it will keep its old behavior until you restart the browser (at least for Firefox 3.0.6).
After developing a feature branch for Way Too Long, we finally reached our milestone a couple of weeks ago. In the meantime a few patches had been ported back to trunk, but most work had been done in the branch. The easiest way to handle this dependency in Subversion seemed to be to simply switch trunk with the current feature branch, and so we did. It works something along the lines of:
- svn del trunk
- svn commit
- svn mv branches/Name trunk
- svn commit
A handly little recipe can be found at BigSmoke: Replacing SVN trunk with branch. Enjoy!