I also have a problem using YSlow (2.1.0) with downthemall (2.0.7). Downloads
fail with a size discrepancy error.

Hi Francis,

YSlow is now compatible with Firefox up to 6.* (
https://addons.mozilla.org/en-US/firefox/addon/yslow/) starting today.

Regarding the "-" on CDN hostnames, I've just tested with
www.google-analytics.com and works for me, make sure you're following these
steps on http://developer.yahoo.com/yslow/faq.html#faq_cdn (make sure you
restart your firefox before running YSlow again).


Best,

Marcel




On Sat, Jun 25, 2011 at 2:44 AM, francis.pallini
<francis.pallini@...>wrote:

> **
>
>
> Hi,
>
> I am using YSlow 3.0.3 with Firefox 4.0.1 and Firebug 1.7.3.
>
> First of all, thank you for this add-on, the advices are wise and we
> greatly improved the performance of our websites thanks to it.
>
> When will it be compatible with Firefox 5?
>
> Also, CDN hostnames cannot contain '-' characters, otherwise they are not
> recognized.
>
> Kind regards,
>
> Francis.
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

Hi Marcel,

Compatibility is great :-) However, I checked the FAQ and I still encounter the
same problem with CDNs:

  * YSlow 3.0.3 / Firefox 5.0 / Firebug 1.7.3
  * about:config / extensions.yslow.cdnHostnames =
static.experts-delphi.fr,www.google-analytics.com
  * Stopped Firefox, checked the process list, started Firefox
  * Ran a test on http://www.experts-delphi.fr/ and still:

Grade F on Use a Content Delivery Network (CDN)

There are 10 static components that are not on CDN.

Using these CDN hostnames from your preferences:
static.experts-delphi.fr,www.google-analytics.com

     static.experts-delphi.fr: 9 components, 246.8K (37.5K GZip)
     www.google-analytics.com: 1 component, 27.2K (11.7K GZip)

Did I miss something?

Regards,

Francis.

--- In exceptional-performance@yahoogroups.com, Marcel Duran <contact@...>
wrote:
>
> Hi Francis,
>
> YSlow is now compatible with Firefox up to 6.* (
> https://addons.mozilla.org/en-US/firefox/addon/yslow/) starting today.
>
> Regarding the "-" on CDN hostnames, I've just tested with
> www.google-analytics.com and works for me, make sure you're following these
> steps on http://developer.yahoo.com/yslow/faq.html#faq_cdn (make sure you
> restart your firefox before running YSlow again).
>
>
> Best,
>
> Marcel
>
>
>
>
> On Sat, Jun 25, 2011 at 2:44 AM, francis.pallini
> <francis.pallini@...>wrote:
>
> > **
> >
> >
> > Hi,
> >
> > I am using YSlow 3.0.3 with Firefox 4.0.1 and Firebug 1.7.3.
> >
> > First of all, thank you for this add-on, the advices are wise and we
> > greatly improved the performance of our websites thanks to it.
> >
> > When will it be compatible with Firefox 5?
> >
> > Also, CDN hostnames cannot contain '-' characters, otherwise they are not
> > recognized.
> >
> > Kind regards,
> >
> > Francis.
> >
> >
> >
>
>
>
> --
> Marcel Duran
>
>
> [Non-text portions of this message have been removed]
>

Hi,

I´ve found out that YSlow raises an error in the FF error console.

YSlow expects the object FirebugContext, which seems to be removed in
version 1.8:

see here:
http://code.google.com/p/fbug/source/detail?r=9768
<http://code.google.com/p/fbug/source/detail?r=9768>

By changing FirebugContext to Firebug.currentContext in the file:
/chrome/content/yslow-firebug.js  YSlow will work again.

Here is my diff:

26c26
< /*global YSLOW, Firebug, FBL, FirebugContext, content, TabWatcher*/
---
> /*global YSLOW, Firebug, FBL, Firebug.currentContext, content,
TabWatcher*/
74c74
<                 if
(!FirebugContext.getPanel("YSlow").document.yslowContext) {
---
>                 if
(!Firebug.currentContext.getPanel("YSlow").document.yslowContext) {
76c76
<                     panel = FirebugContext.getPanel("YSlow");
---
>                     panel = Firebug.currentContext.getPanel("YSlow");
78c78
<                     panel.document.yslowContext =
FirebugContext.yslowContext;
---
>                     panel.document.yslowContext =
Firebug.currentContext.yslowContext;
134c134
<                 if (win !== FirebugContext.window) {
---
>                 if (win !== Firebug.currentContext.window) {
137c137
<                     fbcontext = FirebugContext;
---
>                     fbcontext = Firebug.currentContext;
139c139
<                 // This cause initialNode to be called, thus creating
FirebugContext.yslowContext.
---
>                 // This cause initialNode to be called, thus creating
Firebug.currentContext.yslowContext.
155c155
<                 if (fbcontext !== FirebugContext) {
---
>                 if (fbcontext !== Firebug.currentContext) {
175c175
<                 if (win !== FirebugContext.window) {
---
>                 if (win !== Firebug.currentContext.window) {
178c178
<                     fbcontext = FirebugContext;
---
>                     fbcontext = Firebug.currentContext;
189c189
<                 if (fbcontext !== FirebugContext) {
---
>                 if (fbcontext !== Firebug.currentContext) {
208c208
<                 FirebugContext.getPanel("YSlow").createProgressBar();
---
>
Firebug.currentContext.getPanel("YSlow").createProgressBar();
212,213c212,213
<                 FirebugContext.getPanel("YSlow").removeProgressBar();
<                 FirebugContext.getPanel("YSlow").doView();
---
>
Firebug.currentContext.getPanel("YSlow").removeProgressBar();
>                 Firebug.currentContext.getPanel("YSlow").doView();
217c217
<
FirebugContext.getPanel("YSlow").setPeelProgress(event_object);
---
>
Firebug.currentContext.getPanel("YSlow").setPeelProgress(event_object);
221c221
<
FirebugContext.getPanel("YSlow").setFetchProgress(event_object);
---
>
Firebug.currentContext.getPanel("YSlow").setFetchProgress(event_object);
225c225
<                 YSLOW.controller.run(FirebugContext.window,
FirebugContext.yslowContext, false);
---
>                 YSLOW.controller.run(Firebug.currentContext.window,
Firebug.currentContext.yslowContext, false);
234c234
<
FirebugContext.getPanel("YSlow").doView("ysStatsButton");
---
>
Firebug.currentContext.getPanel("YSlow").doView("ysStatsButton");
239c239
<
FirebugContext.getPanel("YSlow").doView("ysPerfButton");
---
>
Firebug.currentContext.getPanel("YSlow").doView("ysPerfButton");
279c279
<                 YSLOW.latest_yslowContext =
FirebugContext.yslowContext;
---
>                 YSLOW.latest_yslowContext =
Firebug.currentContext.yslowContext;
283c283
<                 this.document.yslowContext =
FirebugContext.yslowContext;
---
>                 this.document.yslowContext =
Firebug.currentContext.yslowContext;



Best regards

Markus Feicht



[Non-text portions of this message have been removed]

I wonder if I'm missing something obvious but I can't seem to figure out how to
find the actual errors that yslow finds.   I have it installed and can run it
and get a report.

If it tells me:
"1 iframe component with empty link were found" under 'Avoid empty src or href'

how do I determine where this code is that it's referring to?

I've searched for the answer to this for a while and can't seem to get more
details on errors other than that they exist.

Thanks!

Hi,

Great tool I really love it, but there seems to be a bug with the Tools.

I'm using FF 5.0 on Windows XP with Firebug 1.7.3 and Yslow 3.0.3 and if I click
any of the tools under the tools menu it simply opens a blank tab in Firefox and
that's it?

Is this a known bug and will there be a fix for it?

Thanks

Hi Everyone,

We have some great WPO meetups approaching in Boston.  If you are the area
you should check them out:

July 27th - Chris Bowen from Microsoft on IE9 and IE10 performance
improvements
August 24th - Mike Brittain from Etsy on performance culture and tools
September 21st - Mehdi Daoudi from Catchpoint with some performance
monitoring tales

RSVP for all of these here: http://www.meetup.com/Web-Performance-Boston/.
Hope to see you there!

-Jonathan


[Non-text portions of this message have been removed]

Good morning,

I'm seeing a lot of 'failed to create temp dir' errors on the Smush.it service,
though they are intermitted.  Frequent enough to be causing some problems,
though.

Are you aware of any issues with the Smush.it service at the moment?

Cheers,
Alex

I wrote a blog post <http://www.indolering.com/load>  about my
frustrations with YSlow, but I will just quote my main point,

"However, my most serious complaint with Page Speed and YSlow is the way
they present their data.  From this pretty waterfall loading graph
<http://www.webpagetest.org/result/110209_HB_3VWA/1/details/>  one can
see that time spent downloading JS/CSS never goes over 1ms. The total
time *downloading* all JS/CSS is .033 seconds while time spent *waiting*
for the JS/CSS is 4.2 seconds: the majority of the entire page load
time.

To put that in perspective, all of the work one puts into compressing
the text and using a CDN saved about ~0.4 seconds while combining the
JS/CSS would save ~4.0 seconds.  The general recommendation checklists
YSlow and Page Speed offer are useful, but  they should report the
expected speed gains from any given change and prioritize according to a
time/benefit ratio.   Both tools weight their sub-scores, but they do
little to tell a  developer if it is worth their time and processing
power to bring their  etags in-line."

The exceptional-performance team and YSlow were really the first people
to bring attention to these issues.  I really do appreciate your work!

(If the link is considered spamming, go ahead and remove it : )



[Non-text portions of this message have been removed]

Hello there

I am being marked down for using jQuery Templates
These are in-line script tags which are used to template json data for display
on a mobile device

e.g.
<script id="movieTemplate" type="text/x-jquery-tmpl">
     {{tmpl "summaryTemplate"}}
     <tr><td>Director: ${Director}</td></tr>
</script>

should I be penalised for this or is there a way to declare my usage as ok?

Many thanks, Ant

In the "limitations" table at http://developer.yahoo.com/yslow/limitations/ ,
there is a column for HAR.  Is it possible to run yslow against a har file, and
if so is there any documentation or discussion on how to do this?  I'm
interested in running this server-side against har files that we're generating.

Thank you
Nathan

On Wednesday, 20 July 2011, indolering <zachlym@...> wrote:

> To put that in perspective, all of the work one puts into compressing
> the text and using a CDN saved about ~0.4 seconds while combining the
> JS/CSS would save ~4.0 seconds.  The general recommendation checklists
> YSlow and Page Speed offer are useful, but  they should report the
> expected speed gains from any given change and prioritize according to a
> time/benefit ratio.   Both tools weight their sub-scores, but they do
> little to tell a  developer if it is worth their time and processing
> power to bring their  etags in-line."
>

The actual benefit you'll get depends on where your users are, their
bandwidth, latency, browser, and other characteristics of their
computing set up.  This cannot be determined through static analysis.

--
hello world

hi Nathan,

Yes, running YSlow on command line against HAR file is going to be released
Aug/Sept this year.  YSlow team presented a sneak peak demo of this feature
during Velocity 2011, you can view the video here:
http://www.youtube.com/watch?v=af_udB9XTZI  (the har support feature is at
around 5:25m in the video)

Keep up-to-date with the latest YSlow announcements by:

Visiting the redesigned YSlow page at getyslow.com
Liking YSlow on Facebook: facebook.com/getyslow
Following YSlow on Twitter: twitter.com/getyslow

thanks,
-betty


--- In exceptional-performance@yahoogroups.com, "nathanjwray" <nwray@...> wrote:
>
> In the "limitations" table at http://developer.yahoo.com/yslow/limitations/ ,
there is a column for HAR.  Is it possible to run yslow against a har file, and
if so is there any documentation or discussion on how to do this?  I'm
interested in running this server-side against har files that we're generating.
>
> Thank you
> Nathan
>

hi Alex,

Thanks for reporting this bug.  The fix is in QA cycle and it will go live early
August.

We will post announcement with release updates in the group.

thank you,
-betty tso

--- In exceptional-performance@yahoogroups.com, "alexdunae" <alex@...> wrote:
>
> Good morning,
>
> I'm seeing a lot of 'failed to create temp dir' errors on the Smush.it
service, though they are intermitted.  Frequent enough to be causing some
problems, though.
>
> Are you aware of any issues with the Smush.it service at the moment?
>
> Cheers,
> Alex
>

hi,

Thanks for reporting this bug - it's fixed and submitted to Firefox Add-on
committee for review.  Once it's approved, it will go live.

Keep up-to-date with the latest YSlow announcements by:

Visiting the redesigned YSlow page at getyslow.com
Liking YSlow on Facebook: facebook.com/getyslow
Following YSlow on Twitter: twitter.com/getyslow

thanks,
-betty tso

--- In exceptional-performance@yahoogroups.com, "max peters" <maxjpeters@...>
wrote:
>
> Hi,
>
> Great tool I really love it, but there seems to be a bug with the Tools.
>
> I'm using FF 5.0 on Windows XP with Firebug 1.7.3 and Yslow 3.0.3 and if I
click any of the tools under the tools menu it simply opens a blank tab in
Firefox and that's it?
>
> Is this a known bug and will there be a fix for it?
>
> Thanks
>

hi,

For this particular case - "1 iframe component with empty link were found", try
this:
- view html source code
- perform a search in the source code for "<iframe>" and the one with no value
set for iframe's link/src is what you're looking for.

hope that helps,
-betty tso

--- In exceptional-performance@yahoogroups.com, "turnonthbrightlights"
<csthacker@...> wrote:
>
> I wonder if I'm missing something obvious but I can't seem to figure out how
to find the actual errors that yslow finds.   I have it installed and can run it
and get a report.
>
> If it tells me:
> "1 iframe component with empty link were found" under 'Avoid empty src or
href'
>
> how do I determine where this code is that it's referring to?
>
> I've searched for the answer to this for a while and can't seem to get more
details on errors other than that they exist.
>
> Thanks!
>

Dear sir.

I use the Mobile YSlow to test the mobile website performance. It's
amazing!!!




However, I found the Big bug about gZip compression.

Before/After installing the Gzip component, the size of JavaScript file
are  same.

What happen? :-(




I guess... the header information that the
http://query.yahooapis.com/v1/public/yql
<http://query.yahooapis.com/v1/public/yql>  analyzes is  wrong.

There is no content-length value.




Could you give the solution for me?




Best regards.



[Non-text portions of this message have been removed]

Thanks for reporting, I'll investigate the issue and file a bug for that,
once fixed I'll let you know.

Best,

Marcel

On Sun, Jul 31, 2011 at 9:29 PM, hamul82 <hamul82@...> wrote:

> **
>
>
>
> Dear sir.
>
> I use the Mobile YSlow to test the mobile website performance. It's
> amazing!!!
>
> However, I found the Big bug about gZip compression.
>
> Before/After installing the Gzip component, the size of JavaScript file
> are same.
>
> What happen? :-(
>
> I guess... the header information that the
> http://query.yahooapis.com/v1/public/yql
> <http://query.yahooapis.com/v1/public/yql> analyzes is wrong.
>
> There is no content-length value.
>
> Could you give the solution for me?
>
> Best regards.
>
> [Non-text portions of this message have been removed]
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

I've just installed 5.01 and YSLow nolonger runs. When i click on the YSLow icon
in the footer bar it just pops up a blank toolbar saying Run | close.

When I launch it from Firebug by the menu, I get the usual YSlow window but
hitting the run button or any of the tabs has no effect.

When I detach the YSLOW window from Firebug into its own window, YSlow loses all
formatting / CSS and just becomes a list of left justified <li> elements on a
white background

Any clues to how i can fully uninstall and re-apply so as to get YSlow back...

Am I doing something wrong or...? :)

I've been using yslow for a bit and I like it a lot - recently I can't seem to
be able to use it.

"User experience" is as follows: no results show in the status bar, the firebug
window contains the welcome page with the "run test" button but nothing happens
if I click on it (it doesn't react in any perceivable way).
Using the rules combobox, printable view or clicking the checkbox have the
expected result (well, printable says "run the test"), as well as clicking on
the tabs above.

The error console reports "FirebugContext is not defined" if I click on the "run
test" button - it happens with a couple other Fbug extensions, too. I'm not sure
if it's FF5 related because (my bad) I did not realize I had upgraded :O I'm
using firebug continuosly and that works perfectly fine.

Versions:
YSlow 3.0.3 (just d/l it again to be sure)
FF5 (5.0, last version according to mozilla)
Firebug 1.8.0 (last stable version afaik)

Any clue? Am I doing something wrong? Thanks!

I've run into a strange issue that I cannot seem to resolve.  On three different
machines YSlow has apparently stopped working after I've been using it for a
while.  It's almost as if I've hit some sort of usage limit, which would be
quite odd.

I have tried numerous restarts, disabling and enabling YSlow and Firebug, and
even rebooting one of the machines, but I can't seem to get YSlow to start
working again.  Any suggestions on where to look, what to check, etc. would be
greatly appreciated.

Thanks,

Skip

Would you mind pointing the website and components your testing?

YQL seems to be fetching the gzip size information correctly:

http://developer.yahoo.com/yql/console/?q=show%20tables&env=store://datatables.o\
rg/alltableswithkeys#h=select%20*%20from%20data.headers%20where%20url%3D%22http%\
3A//l.yimg.com/d/lib/bc/bc_2.0.5.js%22

Best,

Marcel

On Sun, Jul 31, 2011 at 9:29 PM, hamul82 <hamul82@...> wrote:

> **
>
>
>
> Dear sir.
>
> I use the Mobile YSlow to test the mobile website performance. It's
> amazing!!!
>
> However, I found the Big bug about gZip compression.
>
> Before/After installing the Gzip component, the size of JavaScript file
> are same.
>
> What happen? :-(
>
> I guess... the header information that the
> http://query.yahooapis.com/v1/public/yql
> <http://query.yahooapis.com/v1/public/yql> analyzes is wrong.
>
> There is no content-length value.
>
> Could you give the solution for me?
>
> Best regards.
>
> [Non-text portions of this message have been removed]
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

Windows 7
Firefox 5.0
Firebug 1.8.0
YSlow 3.0.3
Page Speed 1.11.2.2

You can't click the button.

Hi,

A GTmetrix user just reported this issue to us: if a resource has both a
Expires and Cache-Control max-age headers, but the Expires header is not
in the 'far future,' but max-age is, then the resource gets flagged.

Taking a look at the code in yslow/component.js, we have:

      // expiration based on either Expires or Cache-control headers
      expires = that.headers.Expires;
      if (expires && expires.length > 0) {
          // set expires as a JS object
          that.expires = new Date(expires);
          if (that.expires.toString() === 'Invalid Date') {
              that.expires = that.getMaxAge();
          }
      } else {
          that.expires = that.getMaxAge();
      }

which shows that it will take the Expires header over the Cache-Control
max-age header.  However, RFC2616 section 14.9.3 says:

"If a response includes both an Expires header and a max-age directive,
the max-age directive overrides the Expires header, even if the Expires
header is more restrictive."

So shouldn't the Cache-Control max-age header override the Expires header?

Adrian

I think the important question here isn't "what dies the RFC state?" but rather,
"how do the browsers behave?" Given the many areas where browsers differently
Interpret the RFCs, I would not want to rely on this, and would choose to use
only aspires tag.

Of course I'll pragmatically change my opinion when the next browser officer
forces me to ;-)


Peter

On Aug 9, 2011, at 4:55 PM, Adrian Yee <adrian@...> wrote:

> Hi,
>
> A GTmetrix user just reported this issue to us: if a resource has both a
> Expires and Cache-Control max-age headers, but the Expires header is not
> in the 'far future,' but max-age is, then the resource gets flagged.
>
> Taking a look at the code in yslow/component.js, we have:
>
> // expiration based on either Expires or Cache-control headers
> expires = that.headers.Expires;
> if (expires && expires.length > 0) {
> // set expires as a JS object
> that.expires = new Date(expires);
> if (that.expires.toString() === 'Invalid Date') {
> that.expires = that.getMaxAge();
> }
> } else {
> that.expires = that.getMaxAge();
> }
>
> which shows that it will take the Expires header over the Cache-Control
> max-age header. However, RFC2616 section 14.9.3 says:
>
> "If a response includes both an Expires header and a max-age directive,
> the max-age directive overrides the Expires header, even if the Expires
> header is more restrictive."
>
> So shouldn't the Cache-Control max-age header override the Expires header?
>
> Adrian
>


[Non-text portions of this message have been removed]

win7 firefox5.0 yslow3.0.3

all the button can not click...

YSlow 3.0.3 was FF5 compatible when latest stable Firebug was 1.7.3.
That being said, Firebug team made some major changes in 1.8 and made it
available for FF5 which broke YSlow (see
http://code.google.com/p/fbug/source/detail?r=9768). Users immediately
reported the issue which was detected and fixed timely in YSlow 3.0.4,
however it's not available yet due to every new add-on version submitted to
Mozilla requires full review which might take up to 10 days according to
https://addons.mozilla.org/en-US/developers/docs/policies/reviews#full
Once Mozilla finishes reviewing YSlow 3.0.4 it will be available promptly,
in the meantime you can download it from
https://addons.mozilla.org/en-US/firefox/addon/yslow/versions/3.0.4

We appreciate your patience and will update you when the release is publicly
available.

Thanks,
Yahoo! Exceptional Performance team.

On Wed, Aug 10, 2011 at 7:57 PM, weberypf <weberypf@...> wrote:

> **
>
>
> win7 firefox5.0 yslow3.0.3
>
> all the button can not click...
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

YSlow 3.0.3 was FF5 compatible when latest stable Firebug was 1.7.3.
That being said, Firebug team made some major changes in 1.8 and made it
available for FF5 which broke YSlow (see
http://code.google.com/p/fbug/source/detail?r=9768). Users immediately
reported the issue which was detected and fixed timely in YSlow 3.0.4,
however it's not available yet due to every new add-on version submitted to
Mozilla requires full review which might take up to 10 days according to
https://addons.mozilla.org/en-US/developers/docs/policies/reviews#full
Once Mozilla finishes reviewing YSlow 3.0.4 it will be available promptly,
in the meantime you can download it from
https://addons.mozilla.org/en-US/firefox/addon/yslow/versions/3.0.4

We appreciate your patience and will update you when the release is publicly
available.

Thanks,
Yahoo! Exceptional Performance team.

On Mon, Aug 8, 2011 at 2:00 PM, <vincent@...> wrote:

> **
>
>
> Windows 7
> Firefox 5.0
> Firebug 1.8.0
> YSlow 3.0.3
> Page Speed 1.11.2.2
>
> You can't click the button.
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

YSlow 3.0.3 was FF5 compatible when latest stable Firebug was 1.7.3.
That being said, Firebug team made some major changes in 1.8 and made it
available for FF5 which broke YSlow (see
http://code.google.com/p/fbug/source/detail?r=9768). Users immediately
reported the issue which was detected and fixed timely in YSlow 3.0.4,
however it's not available yet due to every new add-on version submitted to
Mozilla requires full review which might take up to 10 days according to
https://addons.mozilla.org/en-US/developers/docs/policies/reviews#full
Once Mozilla finishes reviewing YSlow 3.0.4 it will be available promptly,
in the meantime you can download it from
https://addons.mozilla.org/en-US/firefox/addon/yslow/versions/3.0.4

We appreciate your patience and will update you when the release is publicly
available.

Thanks,
Yahoo! Exceptional Performance team.

On Mon, Aug 1, 2011 at 3:27 PM, skipsauls <skipsauls@...> wrote:

> **
>
>
> I've run into a strange issue that I cannot seem to resolve. On three
> different machines YSlow has apparently stopped working after I've been
> using it for a while. It's almost as if I've hit some sort of usage limit,
> which would be quite odd.
>
> I have tried numerous restarts, disabling and enabling YSlow and Firebug,
> and even rebooting one of the machines, but I can't seem to get YSlow to
> start working again. Any suggestions on where to look, what to check, etc.
> would be greatly appreciated.
>
> Thanks,
>
> Skip
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]

YSlow 3.0.3 was FF5 compatible when latest stable Firebug was 1.7.3.
That being said, Firebug team made some major changes in 1.8 and made it
available for FF5 which broke YSlow (see
http://code.google.com/p/fbug/source/detail?r=9768). Users immediately
reported the issue which was detected and fixed timely in YSlow 3.0.4,
however it's not available yet due to every new add-on version submitted to
Mozilla requires full review which might take up to 10 days according to
https://addons.mozilla.org/en-US/developers/docs/policies/reviews#full
Once Mozilla finishes reviewing YSlow 3.0.4 it will be available promptly,
in the meantime you can download it from
https://addons.mozilla.org/en-US/firefox/addon/yslow/versions/3.0.4

We appreciate your patience and will update you when the release is publicly
available.

Thanks,
Yahoo! Exceptional Performance team.

On Wed, Aug 3, 2011 at 11:55 PM, AlexR <alexbecc@...> wrote:

> **
>
>
> Am I doing something wrong or...? :)
>
> I've been using yslow for a bit and I like it a lot - recently I can't seem
> to be able to use it.
>
> "User experience" is as follows: no results show in the status bar, the
> firebug window contains the welcome page with the "run test" button but
> nothing happens if I click on it (it doesn't react in any perceivable way).
> Using the rules combobox, printable view or clicking the checkbox have the
> expected result (well, printable says "run the test"), as well as clicking
> on the tabs above.
>
> The error console reports "FirebugContext is not defined" if I click on the
> "run test" button - it happens with a couple other Fbug extensions, too. I'm
> not sure if it's FF5 related because (my bad) I did not realize I had
> upgraded :O I'm using firebug continuosly and that works perfectly fine.
>
> Versions:
> YSlow 3.0.3 (just d/l it again to be sure)
> FF5 (5.0, last version according to mozilla)
> Firebug 1.8.0 (last stable version afaik)
>
> Any clue? Am I doing something wrong? Thanks!
>
>
>



--
Marcel Duran


[Non-text portions of this message have been removed]