You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In FB2 we could choose to display the inspector with the Style/Computed/... panel under the source one, rather than side to side. Looks like this:
But in FB3 I'm unable to find the equivalent of the involved option, (a bit misleadingly) named "Vertical panels'. So for the same page as above I inevitably get this:
At my eyes, for most cases the first solution is better, essentially because it gives the source part text much more readable without having to horizontally scroll.
Maybe the option exists in FB3 and I missed it?
Otherwise it would be fine to get it re-included.
Fred
The text was updated successfully, but these errors were encountered:
Useless XHRs in console + this non customizable layout still make me use FB2. On my 2560px width screen I have to use only horizontal view :(
Jumping "Clear" button in "console" and "network" tabs makes me mad, when I have to look for it 1000 times a day. Why not make it in one place on every tab?
Tiny objects viewer in console isn't also handy at all.
Tried to move to FB3 several times. But after a week of struggling return back.
FB2 is perfect. Except absence of js events in html tab.
When debugging js events I have to use Firefox inspector. In other cases FB2 is beyond comparison.
In FB2 we could choose to display the inspector with the Style/Computed/... panel under the source one, rather than side to side. Looks like this:
But in FB3 I'm unable to find the equivalent of the involved option, (a bit misleadingly) named "Vertical panels'. So for the same page as above I inevitably get this:
At my eyes, for most cases the first solution is better, essentially because it gives the source part text much more readable without having to horizontally scroll.
Maybe the option exists in FB3 and I missed it?
Otherwise it would be fine to get it re-included.
Fred
The text was updated successfully, but these errors were encountered: