You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ed <ed...@kdtc.net> on 2010/01/07 05:21:02 UTC
Re: Mailing list archives broken for this list at Apache.org.
Karl Fogel wrote:
> Not sure of the proper place to report this, and subversion.apache.org
> doesn't say (which is in itself a bug, though one that's likely to get
> fixed soon), so I'm posting here (in case it helps for anyone to know),
> and I'll post separately to Apache's infrastructure list.
>
> In Firefox 3.5.6, I visited
>
> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/browser
>
> and clicked on one of the messages (let's pick one at random):
I'm using Seamonkey 1.1.16 and I'm getting a correctly rendered
message here if I select any message.
However, clicking on the following link :
>
> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/ajax/%3C4B42936D.10107@mark.mielke.cc%3E
produces what you see in the following description:
>
> The message is displayed in a horribly broken way in the browser. At
> the top, the browser shows a warning bar that says "This XML file does
> not appear to have any style information associated with it. The
> document tree is shown below.". Below that, it... shows the document
> tree, complete with angle brackets and attributes and everything. The
> body of the message is visible, sort of, but this is surely not the
> intended UI :-).
But what I don't know how to produce is how to get from the first link
to the second link without clicking directly on the second link.
Clicking on the first link, and then clicking on subsequent links
(any one) produces a proper UI and message display.
Edmund
Re: Mailing list archives broken for this list at Apache.org.
Posted by Ed <ed...@kdtc.net>.
Mark Mielke wrote:
> On 01/07/2010 12:21 AM, Ed wrote:
>> Karl Fogel wrote:
>>
>>>
>>> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/ajax/%3C4B42936D.10107@mark.mielke.cc%3E
>>>
>>
>> produces what you see in the following description:
>>
>>>
>>> The message is displayed in a horribly broken way in the browser. At
>>> the top, the browser shows a warning bar that says "This XML file does
>>> not appear to have any style information associated with it. The
>>> document tree is shown below.". Below that, it... shows the document
>>> tree, complete with angle brackets and attributes and everything. The
>>> body of the message is visible, sort of, but this is surely not the
>>> intended UI :-).
>>
>> But what I don't know how to produce is how to get from the first link
>> to the second link without clicking directly on the second link.
>> Clicking on the first link, and then clicking on subsequent links
>> (any one) produces a proper UI and message display.
>
> If you note the /ajax/, I think it's pretty clear that the intent is for
> the browser to invoke java script which downloads the contents as XML,
> extracts it with JavaScript to convert it into pretty DHTML probably
> using the DOM API.
>
> A user would not look at /ajax/ directly. Only the JavaScript on the
> page would pull open that .xml and unpack it as DHTML.
>
Didn't really pay attention to the link itself. Just the results.
Anyway, figured out why and it's exactly as you described it.
(Of course, I didn't use the concise jargon. :))
Edmund
Re: Mailing list archives broken for this list at Apache.org.
Posted by Mark Mielke <ma...@mark.mielke.cc>.
On 01/07/2010 12:47 AM, Mark Mielke wrote:
> On 01/07/2010 12:21 AM, Ed wrote:
>> But what I don't know how to produce is how to get from the first link
>> to the second link without clicking directly on the second link.
>> Clicking on the first link, and then clicking on subsequent links
>> (any one) produces a proper UI and message display.
>
> If you note the /ajax/, I think it's pretty clear that the intent is
> for the browser to invoke java script which downloads the contents as
> XML, extracts it with JavaScript to convert it into pretty DHTML
> probably using the DOM API.
>
> A user would not look at /ajax/ directly. Only the JavaScript on the
> page would pull open that .xml and unpack it as DHTML.
If you look at the HTML directly, it says:
<a onclick="javascript:toggleMessage(1); return false;"
href="ajax/%3c4DF6734D-0402-4C2C-8D15-D6FE14265B0E@mail.utexas.edu%3e">Subversion
in 2010</a>
The "href" is shown in the browser window, but HTML events normally run
the onclick= first, and the "; return false;" means that the event is
processed and will not normally be dropped down to the <a> anchor to
process the href. Therefore, the "href" is displayed on mouse over, but
not normally accessed by a JavaScript-enabled browser.
Maybe the original poster has JavaScript disabled.
Cheers,
mark
--
Mark Mielke<ma...@mielke.cc>
Re: Mailing list archives broken for this list at Apache.org.
Posted by Mark Mielke <ma...@mark.mielke.cc>.
On 01/07/2010 12:21 AM, Ed wrote:
> Karl Fogel wrote:
>
>>
>> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/ajax/%3C4B42936D.10107@mark.mielke.cc%3E
>>
>
> produces what you see in the following description:
>
>>
>> The message is displayed in a horribly broken way in the browser. At
>> the top, the browser shows a warning bar that says "This XML file does
>> not appear to have any style information associated with it. The
>> document tree is shown below.". Below that, it... shows the document
>> tree, complete with angle brackets and attributes and everything. The
>> body of the message is visible, sort of, but this is surely not the
>> intended UI :-).
>
> But what I don't know how to produce is how to get from the first link
> to the second link without clicking directly on the second link.
> Clicking on the first link, and then clicking on subsequent links
> (any one) produces a proper UI and message display.
If you note the /ajax/, I think it's pretty clear that the intent is for
the browser to invoke java script which downloads the contents as XML,
extracts it with JavaScript to convert it into pretty DHTML probably
using the DOM API.
A user would not look at /ajax/ directly. Only the JavaScript on the
page would pull open that .xml and unpack it as DHTML.
Cheers,
mark
--
Mark Mielke<ma...@mielke.cc>
Re: Mailing list archives broken for this list at Apache.org.
Posted by Karl Fogel <kf...@red-bean.com>.
Karl Fogel <kf...@red-bean.com> writes:
>"Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
>>You may also want to contact the mod_mbox folks: http://httpd.apache.org/mod_mbox/
>
>Done.
To be clearer: https://issues.apache.org/bugzilla/show_bug.cgi?id=48500
-K
Re: Mailing list archives broken for this list at Apache.org.
Posted by Karl Fogel <kf...@red-bean.com>.
"Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
>You may also want to contact the mod_mbox folks: http://httpd.apache.org/mod_mbox/
Done.
Re: Mailing list archives broken for this list at Apache.org.
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Jan 7, 2010, at 12:00 AM, Karl Fogel wrote:
> Ed <ed...@kdtc.net> writes:
>> Correction. Now I know how to reproduce this.
>>
>> Select the first link. Right click on one message (any one will
>> do) and the select Open in New Tab or Open in New Window. Then
>> presto, what is seen in the second link.
>>
>> Is it a bug, or is it just the actual display of what the
>> link produces?
>>
>> Since in the browser, the javascript takes the linked
>> (XML document) and displays it properly. So if you just
>> view the link without being processed by the javascript,
>> which (AFAIK) displays the XML in its natural state.
>>
>> That's what I think happens.
>
> Thank you! Yes, I was right-clicking to open in a new tab -- I should
> have specified that, but it was unconscious, so I wasn't aware of it
> until you figured it out above.
>
> I'll follow up with Apache Infrastructure telling them the diagnosis.
You may also want to contact the mod_mbox folks: http://httpd.apache.org/mod_mbox/
-Hyrum
Re: Mailing list archives broken for this list at Apache.org.
Posted by Karl Fogel <kf...@red-bean.com>.
Ed <ed...@kdtc.net> writes:
>Correction. Now I know how to reproduce this.
>
>Select the first link. Right click on one message (any one will
>do) and the select Open in New Tab or Open in New Window. Then
>presto, what is seen in the second link.
>
>Is it a bug, or is it just the actual display of what the
>link produces?
>
>Since in the browser, the javascript takes the linked
>(XML document) and displays it properly. So if you just
>view the link without being processed by the javascript,
>which (AFAIK) displays the XML in its natural state.
>
>That's what I think happens.
Thank you! Yes, I was right-clicking to open in a new tab -- I should
have specified that, but it was unconscious, so I wasn't aware of it
until you figured it out above.
I'll follow up with Apache Infrastructure telling them the diagnosis.
-Karl
Re: Mailing list archives broken for this list at Apache.org.
Posted by Ed <ed...@kdtc.net>.
Mark Mielke wrote:
> On 01/07/2010 12:30 AM, Ed wrote:
>> Correction. Now I know how to reproduce this.
>>
>> Select the first link. Right click on one message (any one will
>> do) and the select Open in New Tab or Open in New Window. Then
>> presto, what is seen in the second link.
>>
>> Is it a bug, or is it just the actual display of what the
>> link produces?
>>
>> Since in the browser, the javascript takes the linked
>> (XML document) and displays it properly. So if you just
>> view the link without being processed by the javascript,
>> which (AFAIK) displays the XML in its natural state.
>>
>> That's what I think happens.
>
> Haha - I should have waited one more minute to see your post. If you
> look to my post, it only overrides "onclick". It does not override
> "right click". So, yes, it seems like a limitation of the
> implementation. Only a regular click is handled properly. A right click
> open new window does not execute the JavaScript, and therefore falls to
> the href which is not presentable without a style sheet.
Exactly. Wish I had the written it properly. Just re-read
what I wrote and noticed that it's grammatically incorrect.
*sigh* My bad.
Edmund
Re: Mailing list archives broken for this list at Apache.org.
Posted by Роман Донченко <DX...@yandex.ru>.
Mark Mielke <ma...@mark.mielke.cc> писал в своём письме Thu, 07 Jan 2010
08:53:27 +0300:
> On 01/07/2010 12:30 AM, Ed wrote:
>> Correction. Now I know how to reproduce this.
>>
>> Select the first link. Right click on one message (any one will
>> do) and the select Open in New Tab or Open in New Window. Then
>> presto, what is seen in the second link.
>>
>> Is it a bug, or is it just the actual display of what the
>> link produces?
>>
>> Since in the browser, the javascript takes the linked
>> (XML document) and displays it properly. So if you just
>> view the link without being processed by the javascript,
>> which (AFAIK) displays the XML in its natural state.
>>
>> That's what I think happens.
>
> Haha - I should have waited one more minute to see your post. If you
> look to my post, it only overrides "onclick". It does not override
> "right click". So, yes, it seems like a limitation of the
> implementation. Only a regular click is handled properly. A right click
> open new window does not execute the JavaScript, and therefore falls to
> the href which is not presentable without a style sheet.
I'd say that the problem is not that they don't handle right clicks, but
that they've set the internal URI as the link's target, thus making it
visible for the user. If I were them, I'd put the plain message URI in
there, with the JavaScript constructing the /ajax/ URI when needed.
Also, FWIW, the Ajaxy stuff seems to be browser dependent. In IE, Opera,
and Firefox w/NoScript I just get the plain links (which made me wonder
for a while what's everyone talking about).
Roman.
Re: Mailing list archives broken for this list at Apache.org.
Posted by Mark Mielke <ma...@mark.mielke.cc>.
On 01/07/2010 12:30 AM, Ed wrote:
> Correction. Now I know how to reproduce this.
>
> Select the first link. Right click on one message (any one will
> do) and the select Open in New Tab or Open in New Window. Then
> presto, what is seen in the second link.
>
> Is it a bug, or is it just the actual display of what the
> link produces?
>
> Since in the browser, the javascript takes the linked
> (XML document) and displays it properly. So if you just
> view the link without being processed by the javascript,
> which (AFAIK) displays the XML in its natural state.
>
> That's what I think happens.
Haha - I should have waited one more minute to see your post. If you
look to my post, it only overrides "onclick". It does not override
"right click". So, yes, it seems like a limitation of the
implementation. Only a regular click is handled properly. A right click
open new window does not execute the JavaScript, and therefore falls to
the href which is not presentable without a style sheet.
Cheers,
mark
--
Mark Mielke<ma...@mielke.cc>
Re: Mailing list archives broken for this list at Apache.org.
Posted by Ed <ed...@kdtc.net>.
Ed wrote:
> Karl Fogel wrote:
>> Not sure of the proper place to report this, and subversion.apache.org
>> doesn't say (which is in itself a bug, though one that's likely to get
>> fixed soon), so I'm posting here (in case it helps for anyone to know),
>> and I'll post separately to Apache's infrastructure list.
>>
>> In Firefox 3.5.6, I visited
>>
>> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/browser
>>
>>
>> and clicked on one of the messages (let's pick one at random):
>
> I'm using Seamonkey 1.1.16 and I'm getting a correctly rendered
> message here if I select any message.
>
> However, clicking on the following link :
>
>>
>> http://mail-archives.apache.org/mod_mbox/subversion-dev/201001.mbox/ajax/%3C4B42936D.10107@mark.mielke.cc%3E
>>
>
> produces what you see in the following description:
>
>>
>> The message is displayed in a horribly broken way in the browser. At
>> the top, the browser shows a warning bar that says "This XML file does
>> not appear to have any style information associated with it. The
>> document tree is shown below.". Below that, it... shows the document
>> tree, complete with angle brackets and attributes and everything. The
>> body of the message is visible, sort of, but this is surely not the
>> intended UI :-).
>
> But what I don't know how to produce is how to get from the first link
> to the second link without clicking directly on the second link.
> Clicking on the first link, and then clicking on subsequent links
> (any one) produces a proper UI and message display.
>
Correction. Now I know how to reproduce this.
Select the first link. Right click on one message (any one will
do) and the select Open in New Tab or Open in New Window. Then
presto, what is seen in the second link.
Is it a bug, or is it just the actual display of what the
link produces?
Since in the browser, the javascript takes the linked
(XML document) and displays it properly. So if you just
view the link without being processed by the javascript,
which (AFAIK) displays the XML in its natural state.
That's what I think happens.
Edmund