<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Introduction (and Bugzilla News)</title>
	<atom:link href="http://webkit.org/blog/5/introduction-and-bugzilla-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/</link>
	<description>All about WebKit development</description>
	<pubDate>Fri, 25 Jul 2008 12:48:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: maciej</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-32</link>
		<dc:creator>maciej</dc:creator>
		<pubDate>Sat, 09 Jul 2005 21:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-32</guid>
		<description>Hi Al,

One good way to report bugs of this sort is http://bugzilla.opendarwin.org . This way you can track progress on your issue and everyone can see the bug report and fix it. It sounds like you have steps to reproduce, so it should be easy to file a good bug report. Once you have that, you can encourage people to work on it. Blog comments are generally not a good way to report bugs. We don't put them into any kind of tracking system so they can esaily get lost.</description>
		<content:encoded><![CDATA[<p>Hi Al,</p>
<p>One good way to report bugs of this sort is <a href="http://bugzilla.opendarwin.org" rel="nofollow">http://bugzilla.opendarwin.org</a> . This way you can track progress on your issue and everyone can see the bug report and fix it. It sounds like you have steps to reproduce, so it should be easy to file a good bug report. Once you have that, you can encourage people to work on it. Blog comments are generally not a good way to report bugs. We don&#8217;t put them into any kind of tracking system so they can esaily get lost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sparber</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-31</link>
		<dc:creator>Sparber</dc:creator>
		<pubDate>Sat, 09 Jul 2005 17:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-31</guid>
		<description>And here is a test case: http://www.projectseven.com/csslab/testing/safari/alignbad.htm

On the first page (alignbad.htm), operate the menu. The first pass through all the levels, alignment of the sub-menus vis a vis the parent, is perfect. That is, it is offset both vertically and horizontally. The second pass through the levels, results in the sub-menus at the third level being misaligned relative to their parents. On page 2 (aligngood.htm) the alignment remains perfect. Embedded in that page are the CSS fixes, so just view source and look for the commented rules.

This anomaly did not occur when we developed and tested this product. Testing was done on Jaguar and early versions of Panther. Jaguar is still perfect, while Panther Safari has been updated somewhere along the line with a change that causes this problem. We have no idea what Tiger versions are doing.

Do you have a reason for this anomaly (all other browsers are fine and have been all along)?

Al Sparber</description>
		<content:encoded><![CDATA[<p>And here is a test case: <a href="http://www.projectseven.com/csslab/testing/safari/alignbad.htm" rel="nofollow">http://www.projectseven.com/csslab/testing/safari/alignbad.htm</a></p>
<p>On the first page (alignbad.htm), operate the menu. The first pass through all the levels, alignment of the sub-menus vis a vis the parent, is perfect. That is, it is offset both vertically and horizontally. The second pass through the levels, results in the sub-menus at the third level being misaligned relative to their parents. On page 2 (aligngood.htm) the alignment remains perfect. Embedded in that page are the CSS fixes, so just view source and look for the commented rules.</p>
<p>This anomaly did not occur when we developed and tested this product. Testing was done on Jaguar and early versions of Panther. Jaguar is still perfect, while Panther Safari has been updated somewhere along the line with a change that causes this problem. We have no idea what Tiger versions are doing.</p>
<p>Do you have a reason for this anomaly (all other browsers are fine and have been all along)?</p>
<p>Al Sparber</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sparber</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-30</link>
		<dc:creator>Sparber</dc:creator>
		<pubDate>Sat, 09 Jul 2005 16:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-30</guid>
		<description>I saw this yesterday on Zeldman's A list Apart: "If you’re using Safari 1.3 or 2.0, the subnavigation in our sidebar starts in the wrong place, and the diamond markers preceding each list item are superimposed over the crack between columns. Dave Hyatt, Apple’s Safari chief, fixed the bug the same day we reported it. Updated versions of Safari 1.3/2, free of said bug, will become available very soon." Is there a method we can use to report DOM issues that are causing the behavior of our products to change from one Safari version and OS to another? And to get souch good response time? We'd like to play by the rules but are confused as to how bugs and issues are both reported and prioritized.

Thanks
Al Sparber</description>
		<content:encoded><![CDATA[<p>I saw this yesterday on Zeldman&#8217;s A list Apart: &#8220;If you’re using Safari 1.3 or 2.0, the subnavigation in our sidebar starts in the wrong place, and the diamond markers preceding each list item are superimposed over the crack between columns. Dave Hyatt, Apple’s Safari chief, fixed the bug the same day we reported it. Updated versions of Safari 1.3/2, free of said bug, will become available very soon.&#8221; Is there a method we can use to report DOM issues that are causing the behavior of our products to change from one Safari version and OS to another? And to get souch good response time? We&#8217;d like to play by the rules but are confused as to how bugs and issues are both reported and prioritized.</p>
<p>Thanks<br />
Al Sparber</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vicki</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-29</link>
		<dc:creator>vicki</dc:creator>
		<pubDate>Wed, 06 Jul 2005 22:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-29</guid>
		<description>Oliver, does this page help?

http://webkit.opendarwin.org/quality/testwriting.html</description>
		<content:encoded><![CDATA[<p>Oliver, does this page help?</p>
<p><a href="http://webkit.opendarwin.org/quality/testwriting.html" rel="nofollow">http://webkit.opendarwin.org/quality/testwriting.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gung Ho For UNIX</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-26</link>
		<dc:creator>Gung Ho For UNIX</dc:creator>
		<pubDate>Fri, 01 Jul 2005 16:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-26</guid>
		<description>&lt;strong&gt;WebKit now gold standard for open source bug reporting&lt;/strong&gt;

Big holler out to Maciej Stachowiak, a new contributor on the revamped Surfin' Safari blog:

http://webkit.opendarwin.org/blog/?p=5

They've really set a high standard for active engagement in, and education about,  the bug process:

 http://webkit.o...</description>
		<content:encoded><![CDATA[<p><strong>WebKit now gold standard for open source bug reporting</strong></p>
<p>Big holler out to Maciej Stachowiak, a new contributor on the revamped Surfin&#8217; Safari blog:</p>
<p><a href="http://webkit.opendarwin.org/blog/?p=5" rel="nofollow">http://webkit.opendarwin.org/blog/?p=5</a></p>
<p>They&#8217;ve really set a high standard for active engagement in, and education about,  the bug process:</p>
<p> <a href="http://webkit.o.." rel="nofollow">http://webkit.o..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rtmfd</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-21</link>
		<dc:creator>rtmfd</dc:creator>
		<pubDate>Fri, 01 Jul 2005 01:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-21</guid>
		<description>Hey Maciej, still hangout in #kitchenstadium?</description>
		<content:encoded><![CDATA[<p>Hey Maciej, still hangout in #kitchenstadium?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlthA</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-17</link>
		<dc:creator>AlthA</dc:creator>
		<pubDate>Thu, 30 Jun 2005 11:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-17</guid>
		<description>This seems like volunteering? Let's write one!</description>
		<content:encoded><![CDATA[<p>This seems like volunteering? Let&#8217;s write one!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-16</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Thu, 30 Jun 2005 08:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-16</guid>
		<description>Hehe, we also need clear documentation on how to make webkit test cases :)</description>
		<content:encoded><![CDATA[<p>Hehe, we also need clear documentation on how to make webkit test cases <img src='http://webkit.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlthA</title>
		<link>http://webkit.org/blog/5/introduction-and-bugzilla-news/#comment-14</link>
		<dc:creator>AlthA</dc:creator>
		<pubDate>Thu, 30 Jun 2005 05:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.opendarwin.org/blog/?p=5#comment-14</guid>
		<description>In my humble opinion, everyone should read thesse documents before they get canconfirm and editbugs rights in Bugzilla :).</description>
		<content:encoded><![CDATA[<p>In my humble opinion, everyone should read thesse documents before they get canconfirm and editbugs rights in Bugzilla :).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
