why not report this bug to firefox developers?
On 10/25/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
this same problem (of needing nbsp to display empty table cells) occurred
back in the days of Netscape 4.7.
It would suck if they've regressed back to that.
Back then, we had to solve this by
thanks adam
useful hints as usual
On 10/25/06, Adam Winer [EMAIL PROTECTED] wrote:
Arash,
No, there isn't a conflict. Code looking for translations will all
use UIViewRoot.getLocale().
BTW, for reading direction, we already have a RequestContext
getReadingDirection() that can be overridden
I like #2 because:
1. no new public apis.
2. correct behaviour out-of-the-box
3. we won't get into a weird state where locale is english_uk, but someone
programmatically sets formatting locale to english_us.
--arjuna
On 10/23/06, Adam Winer [EMAIL PROTECTED] wrote:
Arash,
Arj,
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no way to add this feature without adding a public API.
The question is entirely what the behavior of that
On 10/24/06, Adam Winer [EMAIL PROTECTED] wrote:
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no way to add this feature without adding a public API.
The
Arjuna Wijeyekoon wrote:
On 10/24/06, Adam Winer [EMAIL PROTECTED] wrote:
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no way to add this feature without
I believe that #1 is what we should do. If you do #2, then the locale
will be changed away from what the view-root offers (and which might
be derived from the accept-header of the request, so you have the
possibility to implement #2) somehow automagically - without the
developer really knowing.
