NoOp wrote:
On 08/01/2011 12:47 PM, Bill Davidsen wrote:
Jens Hatlak wrote:
hawker wrote:
That said 2.2 has had the most regression bugs,
lost features and new bugs of any version I have seen since before 1.0.
I hope this new rapid release is not causing SM quality to suffer and
this is just
Bill Spikowski wrote:
hawker wrote:
As a side note: I hate to complain here. I find most of the
complaining here to
be unwarranted. To read this forum when SM went from 1.x to 2.0 the
sky was
falling. Most of the show stoppers I hear were issues I never saw,
or felt
were not a big deal. So
Jens Hatlak wrote:
hawker wrote:
That said 2.2 has had the most regression bugs,
lost features and new bugs of any version I have seen since before 1.0.
I hope this new rapid release is not causing SM quality to suffer and
this is just a bad build that we will get past. What is the feeling of
On 08/01/2011 12:47 PM, Bill Davidsen wrote:
Jens Hatlak wrote:
hawker wrote:
That said 2.2 has had the most regression bugs,
lost features and new bugs of any version I have seen since before 1.0.
I hope this new rapid release is not causing SM quality to suffer and
this is just a bad build
WLS wrote:
Sorry to burst your bubble, but I want SeaMonkey to do what
all modern browsers are starting to do, such as HTML5, CSS3,
3D, Web video without Flash support and more.
As Jens Hatlak so correctly observed, there may well be sound
/technical/ reasons for wanting to make changes to
Jens Hatlak wrote:
2.2 was the first release after we switched to the rapid release process,
Jens, can you say more about this switch to the rapid release process, for
the benefit of those of us who are outside the inner circle and are
therefore probably unaware of what this rapid release
Philip TAYLOR (Webmaster, Ret'd) schrieb:
This is rather different to simply
slavishly emulating (or anticipating) what the competition are
already doing or are about to do.
Well, before (with the old search plugin implementation) we slavishly
emulated what Apple had done a long time ago, and
Philip TAYLOR (Webmaster, Ret'd) wrote:
Jens Hatlak wrote:
2.2 was the first release after we switched to the rapid release process,
Jens, can you say more about this switch to the rapid release process, for
the benefit of those of us who are outside the inner circle and are
therefore
Jens Hatlak wrote:
Basically it means that a new major stable version is released every six weeks,
and security updates will only be fixed for that new version; the previous
versions are discontinued instantly. Since the Mozilla platform (the rendering
engine Gecko etc.) is bound to the
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input. This was great if
I wanted to try different search results and not have to either use the
back button or open in new tab/window.
2.2 lost this functionality and the
hawker wrote:
As a side note: I hate to complain here. I find most of the
complaining here to be unwarranted. To read this forum when SM went
from 1.x to 2.0 the sky was falling. Most of the show stoppers I
hear were issues I never saw, or felt were not a big deal. So most
of the gloom and
hawker schrieb:
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input.
Unfortunately that's not possible in this way with the new search
mechanism we switched to in 2.1 and later. This is unfortunate, but OTOH
the older
Robert Kaiser wrote:
hawker schrieb:
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input.
Unfortunately that's not possible in this way with the
new search mechanism we switched to in 2.1 and later.
This is
hawker wrote:
As a side note: I hate to complain here. I find most of the complaining here to
be unwarranted. To read this forum when SM went from 1.x to 2.0 the sky was
falling. Most of the show stoppers I hear were issues I never saw, or felt
were not a big deal. So most of the gloom and doom
On 7/28/2011 12:50 PM, Robert Kaiser wrote:
hawker schrieb:
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input.
Unfortunately that's not possible in this way with the new search
mechanism we switched to in 2.1 and
Philip TAYLOR wrote:
Robert Kaiser wrote:
This is unfortunate, but OTOH the older mechanism couldn't
support the OpenSearch standard all other browser support,
At the risk of sounding confrontational (which is not my intent)
doing what all other browsers do is not, I suggest, why most
of us
hawker wrote:
That said 2.2 has had the most regression bugs,
lost features and new bugs of any version I have seen since before 1.0.
I hope this new rapid release is not causing SM quality to suffer and
this is just a bad build that we will get past. What is the feeling of
the development team
Philip TAYLOR (Webmaster, Ret'd) wrote:
Robert Kaiser wrote:
hawker schrieb:
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input.
Unfortunately that's not possible in this way with the
new search mechanism
On Thu, 28 Jul 2011 18:00:39 +0100, Philip TAYLOR (Webmaster, Ret'd) wrote:
Robert Kaiser wrote:
hawker schrieb:
So in SM 2.0 and before the sidebar search displayed the search results
in both the browser window and below the search input.
Unfortunately that's not possible
19 matches
Mail list logo
