Erik,

my perspective is slightly different to Chaals and Holger.
one reason a bug tracking system should be public is that it enables  
the less skilled person (like me) to know whether a bug has been  
reported.
this way they may be encouraged to develop a test case.
currently about the only simple way I have of recording a bug issue  
is by copying the online report to chaals and yourself in an email.

regarding systemLanguage http://www.peepo.co.uk is a test case and  
this was indicated in the forum and reported in bug #207469
this has worked for some years in ASV3.1, and closely follows your  
suggestion, though perhaps missing some safety checks.
my coding is most likely defective and I would welcome your always  
useful support and comments and shall act on them.

When asserting that elements and attributes are supported it is  
important that there are cogent arguments to sustain decisions and UA  
behaviour. It seems plain that in this instance a decision has not  
been made as to implementation. For this reason it might perhaps be  
more reasonable to state "partial" implementation.

How does one select 'large size' buttons? on OS X?
is this a known bug?

Once again I emphasise that I love Opera, and respect those that sail  
within her.

~:"

Jonathan Chetwynd



On 5 Jul 2006, at 10:20, Erik Dahlström wrote:

On Wed, 05 Jul 2006 10:47:33 +0200, Jonathan Chetwynd
<[EMAIL PROTECTED]> wrote:

> Erik,
>
> the comment wasn't meant to be offensive, rather informative.

I'm not offended in any way, my mission is only to make sure those bugs
are fixed.

> I would strongly recommend making bug reports public.
> in the meantime visit: http://my.opera.com/SVGraphics/forums/
> forum.dml?id=2403
> which is a public Opera SVG bug reporting space :-)

Yes, that's one public place, but it's not a bug-tracking system it's  
just
a forum and it's not the supported way of reporting bugs*. So far the  
bugs
there carry too little information though (no testcases, no info of what
build/platform/etc), but I believe we have fixed some of them already in
spite of this.

> Perhaps a single example one I copied you into when reporting will
> suffice;
> element <text> and attribute systemLanguage support is claimed but at
> least on OS X seems broken.
> http://www.opera.com/docs/specs/svg/

Please explain how it's broken with direct pointers to the SVG spec and
with a testcase. I agree that using multiple accepted languages does  
make
it behave weird. The SVG spec doesn't really cover the case of multiple
accepted languages. If you only pick one language of those that are
accepted, then it follows that you behave strange in the case where the
systemLanguage specifies say the second or third accepted language and
with a default text-element (without systemLanguage) that is not even in
your list of accepted languages.

Pseudo-example:
accepted languages { french, german, swedish }
<switch>
    <text systemLanguage="de">hallo</text>
    <text systemLanguage="sv">hej</text>
    <text>this is the default case</text>
</switch>

Regards
/Erik

*) Bugreports should go here: https://bugs.opera.com/wizard/

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/




-----
To unsubscribe send a message to: svg-developers- 
[EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my  
membership"
----
Yahoo! Groups Links










-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my 
membership"
---- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/svg-developers/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to