669377 - Integer inline preferences have to accept negative numbers

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0a1) Gecko/20110630 Firefox/7.0a1

The widget for integer inline preferences does only accept positive numbers at the moment. As per definition 'Integer' also covers negative values. Not sure how often negative numbers are used but I think there will be use cases. If you don't think so we should mark it as unsigned integer. Right now it's confusing.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to comment #0)
> cases. If you don't think so we should mark it as unsigned integer. Right
> now it's confusing.

Probably that doesn't work because the preferences system doesn't support unsigned integers. So we have to handle negative values.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

It's not that visible and probably rarely used. So I don't think we have to track this for Firefox 7.

Comment 3

[Geoff Lankow (:darktrojan)]

The number control accepts negative numbers, if the min attribute is negative. Not sure what the lowest negative number it will take is, but that's unlikely to matter.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Geoff, can you please clarify when you mark bugs as invalid? There can be still cases when extensions would need a negative value for a number field. So why has this bug been marked as invalid?

Comment 5

[martino87rm]

Hi there, seems this bug is open for a while now... Anyway as predicted my addon requires the integer field to support input of negative numbers (ex. TZ offset in minutes between a client and a server) which isn't possible at the moment.

Although it's not a big deal to solve it from my side with a custom panel, just mentioning that if it was supported my life would have been a bit easier :)

Comment 6

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.