April 28th, 2009
Mozilla have released the latest beta version of popular open-source browser Firefox for testing today.
The most notable change in this version is the increment in version numbers from 3.1b3 to 3.5b4. As noted in my previous post this is due to the inclusion of a number of significant bug fixes and additional features to the code base.
This latest beta includes updates to TraceMonkey, Firefox’s Private Browsing Mode and also support for more CSS and HTML5 attributes. You can read a full list of updates in the beta release notes.
For those interested in downloading and testing this new version, here is the beta release email.
Greetings to all of our great community testers – you are our most
valuable resource. We now have Firefox 3.5 Beta 4 available for testing
(Note: Since my last missive, we have changed the release name to
Firefox 3.5, the release formerly known as Firefox 3.1). Note that this
build is a beta and is intended for pre-release testing. We would like
your help in testing the release and identifying any possible
regressions or issues.
*What to Test/Where to Get Builds**:*
(Note: If you are riding the “beta” channel, you can manually check for
updates and update to this build). Otherwise you will have to download
from the directory below.
http://www.mozilla.com/en-US/firefox/all-beta.html
Please hammer on these builds mercilessly to make sure that things work
well! If you notice things that worked in Firefox 3.1 Beta 3 and do not
work in this release, we would like to know about it right away.
Read the Release Notes
*Please also make sure to read the Release Notes which detail the known
issues: http://en-us.www.mozilla.com/en-US/firefox/3.5b4/releasenotes/
***_How to Report Feedback_:*
(1) File a bug in *https://bugzilla.mozilla.org/. *Note in the comment
if it is a regression from a previous release. Things to remember when
filing a bug:
(a) Always include the Build ID that you tested on. If you type
about: in the URL bar, this will give you the Build ID.
(b) Always include clear Steps to Reproduce the bug
(c) Always check to see if your bug has already been filed. This link
will help: http://tinyurl.com/2465be
(d) Use the regression keyword if it indeed a regression from a
previous release.
(e) If you happen to crash, please include the Breakpad ID in the bug.
You can get this by typing about:crashes in the URL bar.
(2) If you don’t wish to file a bug, report issues through
http://feedback.mozilla.org or through the
mozilla.feedback.firefox.prerelease newsgroup (also available on Google
Groups). However, we prefer bugs as feedback is easier to track.
Thanks in advance to all of you for helping test Firefox and making it
the browser of choice for millions of people all over the world! We are
getting ever closer to the final release and thank you for your
participation.
marcia, on behalf of
Team Mozilla QA
Tags: 3.5, beta, firefox, mozilla
Posted in Mozilla, Tools of the Trade | No Comments »
April 1st, 2009
All websites have a sitemap, the well built ones anyway, usually they are on their own dedicated page and are simply a plain text listing of all the pages within a site, see my sitemap as a basic example.
This is a traditional sitemap, one that you will find on most sites across the internet, there is nothing wrong with this and does its job very well, it lists all my pages within the site allowing people or search engine spiders to navigate around and find the content they are looking for.
There is however a new growing trend, well… I say new but it has been around for a while, but more and more sites seem to be using it recently which has resulted in the “modern sitemap” phrase being termed by the web design and developer community. I’m talking about footer sitemaps, instead of having a single page listing all the pages within a site, you have a smaller “related links” sitemap in the footer of every page on a site, a few examples for you;
- http://www.mozilla.com/
- http://www.apple.com/mac/
- http://www.rednoseday.com/
I can see the benefits of using a sitemap in this way, the first that comes to mind is that you associate the links with some content, search engines can use the content to grab keywords and then serve your links if the keywords are used in a query, this is the big failure of the traditional plain text listing sitemap in terms of SEO, with no content to associate the links to means search engines cant add any weight to the links. Other benefits of this type of sitemap range from providing your visitors a list of related pages they may find useful to simply a way of padding out the footer of your site if you don’t have much content.
As with anything there are downsides to having a sitemap like this, the main one being there isn’t a single point listing all pages within the site, in some cases you may end up overloading a page with links, a big no-no for SEO, not to mention some website designs simply wouldn’t look right with a sitemap in its footer.
I think that while the benifits of having the associated content shouldn’t be ignored, this type of sitemap only works with certain site designs so trying to get a nice balance is what you should aim for, combining the two styles of sitemap to allow your visitors to easily find the content they are looking for. Having a list of all the pages in your site is a valuble tool and allows search engines to index all the pages on your site, having “related links” on a page allows you to show visitors content they may be interested in but wouldnt normally find.
A “modern sitemap” to me is one that users find useful, this could be the traditional sitemap or its younger brother the related links sitemap, the important thing is your visitors can find the content they are looking for.
Tags: modern sitemap, SEO, sitemap, traditional sitemap
Posted in SEO, Website Design | No Comments »