I'd assume the language depends on the http Accept-Language header,
but just changing that doesn't seem sufficient to trigger the bug.

On Jul 27, 3:21 am, Bess <bess...@gmail.com> wrote:
> I don't see that error on mobile Twitter page but I am testing it in
> US.
>
> Do you think it is related to callingURL IP Address? Would Twitter
> process it differently for non-US IP Address on callingURL?
>
> On Jul 26, 2:10 pm, Jonathan del Strother <jdelstrot...@gmail.com>
> wrote:
>
>
>
> > Hi - thanks for the response.  Both the users who have come to us with
> > this problem are non-english speakers - one was definitely viewing it
> > in French, the other claimed to be using English but I kinda suspect a
> > communication problem there...
> > I've not been able to reproduce it, even when setting my phone to
> > different locales - do you have a guaranteed way of reproducing it
> > yet?  Any idea what percentage of users see the problem?  I've been
> > wondering about sticking a ?lang=en parameter in there till it gets
> > fixed.
>
> > -Jonathan
>
> > On Jul 26, 6:49 pm, Matt Harris <thematthar...@twitter.com> wrote:
>
> > > Hi Jonathan,
>
> > > Our mobile team is aware of this issue and is looking into it. From my 
> > > tests
> > > it looks like it only happens for users whose language is not English. Do
> > > you know if these users are viewing the site in anything other than 
> > > English?
>
> > > Thanks
> > > Matt
>
> > > On Mon, Jul 26, 2010 at 12:06 AM, Jonathan del Strother <
>
> > > jdelstrot...@gmail.com> wrote:
> > > > Any further progress on this?  Is there anything I can get my users to
> > > > try, to try & diagnose the problem some more?
>
> > > > -Jonathan
>
> > > > On Jul 22, 3:10 pm, Taylor Singletary <taylorsinglet...@twitter.com>
> > > > wrote:
> > > > > Hi Jonathan,
>
> > > > > One conjecture I can think of based on the screenshot is that this may
> > > > > be due to the broken image upload issues we were having recently --
> > > > > but the further reports on the original link you provided suggest
> > > > > otherwise.
>
> > > > > Looking into this.
>
> > > > > Taylor
>
> > > > > On Thu, Jul 22, 2010 at 3:11 AM, Jonathan del Strother
>
> > > > > <jdelstrot...@gmail.com> wrote:
> > > > > > No takers?
>
> > > > > > On Jul 15, 1:10 pm, Jonathan del Strother <jdelstrot...@gmail.com>
> > > > > > wrote:
> > > > > >> Hi,
> > > > > >> We use Twitter Oauth for third party signin.  I haven't been able 
> > > > > >> to
> > > > > >> reproduce this myself, but one of our users is seeing an error page
> > > > > >> showing "this page contains the following errors: error on line 397
> > > > > >> column 156: opening and ending tag mismatch:divline 0 andstrong".
> > > > > >> Someone at Boxcar seems to be having similar problems -
> > > >http://help.boxcar.io/discussions/problems/455-i-cant-sign-in-in-twitter
>
> > > > > >> Anyone else run into this?  Any suggestions on fixing it?
>
> > > > > >> -Jonathan
>
> > > --
>
> > > Matt Harris
> > > Developer Advocate, Twitterhttp://twitter.com/themattharris

Reply via email to