0.9.3b - error in IE8

77 views
Skip to first unread message

Head United

unread,
Mar 9, 2012, 2:55:08 PM3/9/12
to Treesaver
Hello again,

I'm using the 0.9.3b version of Treesaver as posted by Scott Kellum in
one of the Google Groups discussions.
I'm getting an "Object doesn't support this property or method" error
in IE8 for line 18:

var a=Wa.map(function(a){return"((no-)?"+a+")"})

Unlike errors I've run into in the past, this one completely breaks
Treesaver. I know it's a beta, but is there a fix for this?

Thanks,
Scott

Bram Stein

unread,
Mar 9, 2012, 2:58:31 PM3/9/12
to trees...@googlegroups.com
Hi,

We've dropped IE8 support from 0.9.3b. Is that something that is a
hard requirement for you? We're thinking about putting it back in.

Bram

Head United

unread,
Mar 9, 2012, 3:34:39 PM3/9/12
to Treesaver
Not really. I'm just using 0.9.3b for my studio's blog
(blog.studiofuse.biz), so it's not critical. Our portfolio—which is
more important—is built on 0.9.2, and that of course works fine. I'd
rather see IE8 killed off, anyhow.

Out of curiosity, what's the status of Treesaver? I see from my
various searches that Filipe left last fall for Flipboard. It seems
that only you and Andrea Campi are developing it now, with Scott
Kellum developing a front-end framework.

Anyway, thanks for your work on the project as well as taking the time
to respond to questions.

Regards,
Scott

Ben Schwarz

unread,
Mar 11, 2012, 10:17:19 PM3/11/12
to trees...@googlegroups.com
IE8 is absolutely a real requirement for the application I'm hoping to deploy.
Removing it will remove all viability for using treesaver. 

karen jou

unread,
Mar 31, 2012, 1:11:23 AM3/31/12
to trees...@googlegroups.com
I love the concept of Treesaver being cross-platform.  I cannot consider using Treeviewer if it abandons a browser that is still one of the most popular for our organization.

Scott Kellum

unread,
Apr 2, 2012, 7:24:02 PM4/2/12
to Treesaver
Treesaver is a progressive enhancement tool and does not leave these
users without the content they are seeking. It simply enhances modern
browsers to display the content in a better way. Older browsers can
still view the content in the style of a normal scrolling page. This
page can behave however the designer wants it to behave within the
constraints of that browser.

The decision to remove IE8 and below was because they were holding
Treesaver back from doing things better in current browsers. Again, do
not ignore these users, we do not ignore them in our work and everyone
should be able to view the content no matter what their browser might
be.

MaccG

unread,
Apr 3, 2012, 11:10:15 AM4/3/12
to Treesaver
This is highly disappointing.

yesen

unread,
May 21, 2012, 11:14:34 PM5/21/12
to trees...@googlegroups.com
I will give a thumb for this.  However, will you consider to give out a compatible version which recognize the agent and switch automatically between high performing new version and low performing old version?  As Ben puts, we love treesaver because we can create once and publish almost everywhere.  

在 2012年4月3日星期二UTC+8上午7时24分02秒,Scott Kellum写道:
Reply all
Reply to author
Forward
0 new messages