hi Tobias, Bugzilla has many fields and teams use them in many different
ways. :) It's usually best to let the people reporting or investigating
the bugs update the bug fields.
From my experience, many (most?) teams never change a bug's "Status"
from NEW to ASSIGNED, but they still use "Assign
Hi!
Sorry, I have since some weeks the "can-edit" at Bugzilla and misunderstood the
"Assigned"!
I tried to help and clean up a bit Bugzilla with updating the "Target
Milestone" to a Milestone that get still developed ... and was thinking that
when a bug is "Assigned To", that then the "Status"
What's about the idea (for the future) that all stable versions use XULRunner
and beta, alpha & nightly use there own XUL ???
I think that in the stable versions of Firefox, Thunderbird & Firefox OS are
the Gecko all the same ... ???
This would allow a GUI and running Firfox OS Apps on different
On 2014-07-08, 6:34 PM, L. David Baron wrote:
On Monday 2014-07-07 15:18 -0400, Ehsan Akhgari wrote:
That seems pretty bad. I think we should at least stop supporting
it for Web content. David, what do you think?
I'm ok with restricting it to UA and user style sheets, although if
we're going
On Monday 2014-07-07 15:18 -0400, Ehsan Akhgari wrote:
> That seems pretty bad. I think we should at least stop supporting
> it for Web content. David, what do you think?
I'm ok with restricting it to UA and user style sheets, although if
we're going to do that because of security risks I'd like
Today's MemShrink meeting is brought to you by consolidated JS code:
https://bugzilla.mozilla.org/show_bug.cgi?id=1020012
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measure progress.
*
Regarding the other files there would need to be a versioning scheme
implemented so applications would be able to figure out which one is
compatible. Since any of these applications can be installed stand alone each
one would need to be available during install and update unless we expended
res
OK, I understand.
The question was not just because of FF & TB to save just some bits ...
... it was also, because I think it will be in the future a good idea to let
run Firefox OS Apps on other OSes like it is possible with MS Modern UI and
WinRT ... also would there be a possibility for an al
Tobias Besemer schrieb:
Sorry, maybe a little bit OT ... ;-)
Would it be possible to report back to Mozilla "hanging scripts" ???
I'd love to have something reporting fatal JS error and hanging scripts
but that would be something pretty different from what the current crash
reporter does as t
On 7/8/2014 21:23, Robert Kaiser wrote:
David Rajchenbach-Teller schrieb:
5. Upon the next restart, display a bottom doorhanger on all windows
"Firefox or an add-on encountered a problem [a few seconds ago / on July
4rd, 2014] and recovered. If you wish, Firefox can report it
automatically so th
On 7/8/2014 1:51 PM, Tobias Besemer wrote:
As far as I can remember, at the beginning when GRE was build, there was the
try that Firefox/Thunderbird/Mozilla-Suite will use this ...
After Thunderbird is now back, a "Mozilla Update Service" exist and the Crash
Reporter needs to be re-done, but k
Justin Dolske schrieb:
3) E10S will already need something vaguely like this
That's a completely different subject, esp. as we already have an
in-content crash reporter UI for plugin crashes.
KaiRo
___
dev-platform mailing list
dev-platform@lists.
David Rajchenbach-Teller schrieb:
5. Upon the next restart, display a bottom doorhanger on all windows
"Firefox or an add-on encountered a problem [a few seconds ago / on July
4rd, 2014] and recovered. If you wish, Firefox can report it
automatically so that we can fix the bug ."
This would pro
On 7/8/2014 2:51 PM, Tobias Besemer wrote:
As far as I can remember, at the beginning when GRE was build, there was the
try that Firefox/Thunderbird/Mozilla-Suite will use this ...
After Thunderbird is now back, a "Mozilla Update Service" exist and the Crash
Reporter needs to be re-done, but
Am Dienstag, 8. Juli 2014 20:40:13 UTC+2 schrieb Justin Dolske:
> On 7/8/14 9:56 AM, Tobias Besemer wrote:
>
> > Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
>
> >> 2) Being able to integrate the crash-submission flow into the browser
>
> >> opens up possibilities for better U
As far as I can remember, at the beginning when GRE was build, there was the
try that Firefox/Thunderbird/Mozilla-Suite will use this ...
After Thunderbird is now back, a "Mozilla Update Service" exist and the Crash
Reporter needs to be re-done, but keeps a standalone App for startup problems
o
On 7/8/14 9:56 AM, Tobias Besemer wrote:
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX and features, since it's the
familiar cross-platform environment we all work in.
S
On 7/5/2014 8:21 AM, David Rajchenbach-Teller wrote:
Could we redesign this as follows?
1. Something goes wrong in the code of Firefox;
2. Firefox dies;
3. Crash report is stored to disk, without any dialog;
4. If the crash happened during Firefox shutdown, do nothing, otherwise
restart Firefox
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
> 2) Being able to integrate the crash-submission flow into the browser
> opens up possibilities for better UX and features, since it's the
> familiar cross-platform environment we all work in.
Sorry, maybe a little bit OT ... ;-)
W
- Original Message -
> From: "Justin Dolske"
> To: dev-platform@lists.mozilla.org
> Sent: Tuesday, July 8, 2014 9:23:00 AM
> Subject: Re: Rethinking the crash experience
>
> 3) E10S will already need something vaguely like this, since a
> content-process crash won't take down the whole br
On 7/7/14 12:21 PM, Ehsan Akhgari wrote:
We should keep in mind that sometimes due to startup crashes, we don't
get to run any of the code in Firefox, so we can't gate the crash report
submission on that code at least in the case of startup crashes.
Yes. For that, I think we'll need to retain a
Am Sonntag, 6. Juli 2014 11:08:22 UTC+2 schrieb Neil:
> Since Session Restore already knows things such as the size and position
> of the window it wants to restore, [...]
Some experiences from Win7 64bit:
- During use of FF, FF sometimes "reorder" the windows in my Taskbar.
- FF saves the size o
Something new to this ???
Greets, Tobias.
Am Dienstag, 1. Juli 2014 21:44:16 UTC+2 schrieb Tobias Besemer:
> Am Dienstag, 1. Juli 2014 14:05:39 UTC+2 schrieb David Rajchenbach-Teller:
>
> > Let's concentrate on Session Restore for the moment.
>
>
>
> OK, it was just because of the example an
On 08/07/14 16:25, Tobias Besemer wrote:
> Am Samstag, 5. Juli 2014 14:21:47 UTC+2 schrieb David Rajchenbach-Teller:
>> [...]
>> 3. Crash report is stored to disk, without any dialog;
>> 4. If the crash happened during Firefox shutdown, do nothing, otherwise
>> restart Firefox to its previous state
Am Samstag, 5. Juli 2014 14:21:47 UTC+2 schrieb David Rajchenbach-Teller:
> [...]
> 3. Crash report is stored to disk, without any dialog;
> 4. If the crash happened during Firefox shutdown, do nothing, otherwise
> restart Firefox to its previous state (obviously, we need some measure
> to prevent
On 7/8/2014 9:25 AM, David Rajchenbach-Teller wrote:
Often, we find ourselves attempting to debug JS code that causes a
crash, generally by miscalling a XPCOM component that causes an
assertion failure. Unfortunately, in such cases, the native stack
captured gives little to no indication that ca
Often, we find ourselves attempting to debug JS code that causes a
crash, generally by miscalling a XPCOM component that causes an
assertion failure. Unfortunately, in such cases, the native stack
captured gives little to no indication that can help developers find out
how we reached this specific
On 07/07/14 22:09, Ted Mielczarek wrote:
> I believe this was the primary reasoning behind the current
> implementation (it's been a while, I'm a little fuzzy). We need to
> handle startup crashes, so we need the native crashreporter UI
> regardless of whether we build an in-product crash reporting
28 matches
Mail list logo
