Avatar for Username

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

Cannot View Source Without Issuing New Page Request, making FF Totally Useless for WebApp Development.

terriblysmart
terriblysmart
more options

The question says all there is to be said about it.

This appears to be caused by an over-reaching security policy that has caused nothing but turmoil amongst my development team.

The bug exists somewhere in Mozilla's strategy; You are impeding our ability to reliably test and debug a secure web-app we've been building over the last year. It was frustrating enough fighting with the about:config settings anytime a new version of FF released (every other day recently), but now the issue is compounded.

Pump the brakes guys, you're going the wrong way. We're ditching Firefox-driven testing until you make this right.

Eric

The question says all there is to be said about it. This appears to be caused by an over-reaching security policy that has caused nothing but turmoil amongst my development team. The bug exists somewhere in Mozilla's strategy; You are impeding our ability to reliably test and debug a secure web-app we've been building over the last year. It was frustrating enough fighting with the about:config settings anytime a new version of FF released (every other day recently), but now the issue is compounded. Pump the brakes guys, you're going the wrong way. We're ditching Firefox-driven testing until you make this right. Eric

تمام جوابات (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Is this a new issue in Firefox 26?

When I watch for requests using Fiddler, I'm not seeing a second request when I view source for a few example pages, and the response time implies that I'm seeing a cached page. This may well vary based on cache headers or other factors.

One possible workaround until we figure out what's going on with your application might be to view the source of the rendered DOM. Ctrl+a to select the entire page, right-click, View Selection Source.