https://bugs.documentfoundation.org/show_bug.cgi?id=83904
reported by Beluga.
Can someone test, seems for the whole daily builds 5.x and for the whole
LibreOffice drop-down boxes are broken.
List selection is displayed, but the selection it's not applied neither
change in the box.
If it is,
Hi,
m.a.riosv schrieb:
https://bugs.documentfoundation.org/show_bug.cgi?id=83904
reported by Beluga.
Can someone test, seems for the whole daily builds 5.x and for the whole
LibreOffice drop-down boxes are broken.
List selection is displayed, but the selection it's not applied neither
change
* Present: Stuart, Heiko, Kendy
* UI changes integrated since Wednesday:
+ Add padding between style render and context button (Jay)
* Area Tab design session (Heiko/Jay)
+ Area Tab - https://bugs.documentfoundation.org/show_bug.cgi?id=94551
I'd like to ask for some images of people working on bug triage
process to use them in future bhs banners.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
Hi Regina, thanks for the info.
I think it should be set up as blocker.
Regards
Miguel Ángel.
--
View this message in context:
http://nabble.documentfoundation.org/Drop-down-boxes-are-broken-for-the-whole-LibreOffice-tp4168314p4168321.html
Sent from the QA mailing list archive at Nabble.com.
Hola Miguel Angel
m.a.riosv wrote
> https://bugs.documentfoundation.org/show_bug.cgi?id=83904
> reported by Beluga.
>
> Can someone test, seems for the whole daily builds 5.x and for the whole
> LibreOffice drop-down boxes are broken.
>
> List selection is displayed, but the selection it's
Hi Pedro,
> There is yet another different problem in branch 5.0 (tested in version
> 5.0.4.1 x86): pressing Apply doesn't do anything. So the list works but
> the
> changes are not applied.
Seems you need to click your selection on the list, to get it applied.
Regards.
Miguel Ángel.
--
Robinson Tryon wrote
> As mentioned previously, we're no longer using Severity: 'blocker' to
> mark bugs. Please set those bugs to 'critical' severity.
May I suggest that you migrate all "blockers" to "critical" and remove the
"blocker" option from the list?
It is useless, causes
On 12/04/2015 11:27 AM, m.a.riosv wrote:
>
> I have no rights to do it.
>
> For this I mail in the list, so it can be comment and if it was right set up
> as blocker.
>
> Sounds good the "Ultra-critical", but I don't know if there are already
> enough labels.
You should most definitely have
On Fri, Dec 4, 2015 at 1:40 PM, Joel Madero wrote:
> On 12/04/2015 11:27 AM, m.a.riosv wrote:
>>
>> I have no rights to do it.
>>
>> For this I mail in the list, so it can be comment and if it was right set up
>> as blocker.
As mentioned previously, we're no longer using
On Fri, Dec 4, 2015 at 4:12 PM, Pedro wrote:
> Robinson Tryon wrote
>> As mentioned previously, we're no longer using Severity: 'blocker' to
>> mark bugs. Please set those bugs to 'critical' severity.
>
> May I suggest that you migrate all "blockers" to "critical" and remove
On 12/04/2015 08:22 AM, m.a.riosv wrote:
> Hi Regina, thanks for the info.
>
> I think it should be set up as blocker.
Then set it as a blocker :) But recognize that "blocker" literally has
no meaning (we don't block releases). Ultra-Critical may be a better
term. Either as Critical or Blocker
Hi Joel,
El 04/12/15 a las 19:58, Joel Madero escribió: On 12/04/2015 08:22 AM,
m.a.riosv wrote:
>> Hi Regina, thanks for the info.
>>
>> I think it should be set up as blocker.
>
> Then set it as a blocker :) But recognize that "blocker" literally has
> no meaning (we don't block releases).
13 matches
Mail list logo