<?xml version="1.0"?>
<?xml-stylesheet
href="http://www.w3.org/2000/08/w3c-synd/style.css" type="text/css"
?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel rdf:about="http://pear.php.net/bugs/search.php">
    <title>PEAR Bug Search Results</title>
    <link>http://pear.php.net/bugs/search.php?cmd=display&amp;package_name%5B0%5D=HTML_CSS</link>
    <description>Search Results</description>
    <dc:language>en-us</dc:language>
    <dc:creator>pear-webmaster@lists.php.net</dc:creator>
    <dc:publisher>pear-webmaster@lists.php.net</dc:publisher>
    <admin:generatorAgent rdf:resource="http://pear.php.net/bugs"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
    <items>
     <rdf:Seq>
      <rdf:li rdf:resource="http://pear.php.net/bug/20944" />
      <rdf:li rdf:resource="http://pear.php.net/bug/20087" />
      <rdf:li rdf:resource="http://pear.php.net/bug/16544" />
      <rdf:li rdf:resource="http://pear.php.net/bug/16356" />

     </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://pear.php.net/gifs/pearsmall.gif">
    <title>PEAR Bugs</title>
    <url>http://pear.php.net/gifs/pearsmall.gif</url>
    <link>http://pear.php.net/bugs</link>
  </image>

    <item rdf:about="http://pear.php.net/bug/20944">
      <title>HTML_CSS: Bug 20944 [Open] Redefining already defined constructor for class HTML_CSS</title>
      <link>http://pear.php.net/bugs/20944</link>
      <content:encoded><![CDATA[<pre>HTML_CSS Bug
Reported by tomor
2015-08-31T13:39:01+00:00
PHP: 5.5.28 OS: centos 2.6.32-573.3.1.el6.x86_64 Package Version: 1.5.4

Description:
------------
Since php 5.4 you should not have function __construct and old type constructor - 
method name same as class - HTML_CSS() in one class.

When you do, php generates warning - Redefining already defined constructor for 
class HTML_CSS

I suggest just to delete old type constructor - 
function HTML_CSS($attributes = array(), $errorPrefs = array())

I found old report here - https://pear.php.net/bugs/bug.php?id=16255

Can you create new major version and fix this issue please?

Test script:
---------------
require_once 'HTML/CSS.php';
new HTML_CSS();

Expected result:
----------------
No PHP warning is generated.

Actual result:
--------------
PHP Notice: 
Redefining already defined constructor for class HTML_CSS</pre>]]></content:encoded>
      <description><![CDATA[<pre>HTML_CSS Bug
Reported by tomor
2015-08-31T13:39:01+00:00
PHP: 5.5.28 OS: centos 2.6.32-573.3.1.el6.x86_64 Package Version: 1.5.4

Description:
------------
Since php 5.4 you should not have function __construct and old type constructor - 
method name same as class - HTML_CSS() in one class.

When you do, php generates warning - Redefining already defined constructor for 
class HTML_CSS

I suggest just to delete old type constructor - 
function HTML_CSS($attributes = array(), $errorPrefs = array())

I found old report here - https://pear.php.net/bugs/bug.php?id=16255

Can you create new major version and fix this issue please?

Test script:
---------------
require_once 'HTML/CSS.php';
new HTML_CSS();

Expected result:
----------------
No PHP warning is generated.

Actual result:
--------------
PHP Notice: 
Redefining already defined constructor for class HTML_CSS</pre>]]></description>
      <dc:date>2015-08-31T13:39:01+00:00</dc:date>
      <dc:creator>t &amp;#x61;&amp;#116; tomor &amp;#x64;&amp;#111;&amp;#x74; cz</dc:creator>
      <dc:subject>HTML_CSS Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/20087">
      <title>HTML_CSS: Bug 20087 [Open] Cannot parse some CSS, undefined index</title>
      <link>http://pear.php.net/bugs/20087</link>
      <content:encoded><![CDATA[<pre>HTML_CSS Bug
Reported by marek_sykora
2013-10-07T14:23:11+00:00
PHP: 5.3.14 OS: Ubuntu Package Version: 1.5.4

Description:
------------
1. prepare a CSS using asterix in selector
2. try to parse

Actual result: php fatal error &quot;Undefined index&quot; raises.

Other format rules must be kept to avoid such errors, I found out:
- all regexp chars in selector are dangerous, not only the asterix
- no space between selectors are dangerous, e.g &quot;H1,H2&quot;
- every selector must be on new line

Test script:
---------------
$cssString = '
table * {
  padding: 0
}
';
$parser = new HTML_CSS();
$parser-&gt;parseString($cssString);


Expected result:
----------------
No errors, any CSS string acceptable by browser could be used. 

Workaround: wrap the parser into own class and handle input string to be in 
expected format.

Actual result:
--------------
Php fatal errors.</pre>]]></content:encoded>
      <description><![CDATA[<pre>HTML_CSS Bug
Reported by marek_sykora
2013-10-07T14:23:11+00:00
PHP: 5.3.14 OS: Ubuntu Package Version: 1.5.4

Description:
------------
1. prepare a CSS using asterix in selector
2. try to parse

Actual result: php fatal error &quot;Undefined index&quot; raises.

Other format rules must be kept to avoid such errors, I found out:
- all regexp chars in selector are dangerous, not only the asterix
- no space between selectors are dangerous, e.g &quot;H1,H2&quot;
- every selector must be on new line

Test script:
---------------
$cssString = '
table * {
  padding: 0
}
';
$parser = new HTML_CSS();
$parser-&gt;parseString($cssString);


Expected result:
----------------
No errors, any CSS string acceptable by browser could be used. 

Workaround: wrap the parser into own class and handle input string to be in 
expected format.

Actual result:
--------------
Php fatal errors.</pre>]]></description>
      <dc:date>2013-10-07T14:29:39+00:00</dc:date>
      <dc:creator>marek &amp;#x64;&amp;#111;&amp;#x74; sykora &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>HTML_CSS Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/16544">
      <title>HTML_CSS: Bug 16544 [Open] HTML_CSS undefined index on malformed input</title>
      <link>http://pear.php.net/bugs/16544</link>
      <content:encoded><![CDATA[<pre>HTML_CSS Bug
Reported by brunobg
2009-08-21T18:57:38+00:00
PHP: 5.2.5 OS: Linux Package Version: 1.5.4

Description:
------------
Malformed input generates an E_NOTICE exception with an undefined index. Can be easily fixed by adding one line (at line 2022 of version 1.5.4), marked with FIX below:

           $key = trim($keystr);
	    if (!array_key_exists($key, $atRulesMap)) continue; // FIX
            $parentAtRule = isset($atRulesMap[$key][$i])
                ? $atRulesMap[$key][$i] : $atRulesMap[$key][0];


Test script:
---------------
$parsed = new HTML_CSS();
$parsed-&gt;parseString('function whatever() {
	do_this();
}	');


Expected result:
----------------
No exception thrown.

Actual result:
--------------
Unknown error type: [8] Undefined index:
  Error in line 2023 of file /usr/lib/php/HTML/CSS.php

The exception happens on access to $atRulesMap[$key].</pre>]]></content:encoded>
      <description><![CDATA[<pre>HTML_CSS Bug
Reported by brunobg
2009-08-21T18:57:38+00:00
PHP: 5.2.5 OS: Linux Package Version: 1.5.4

Description:
------------
Malformed input generates an E_NOTICE exception with an undefined index. Can be easily fixed by adding one line (at line 2022 of version 1.5.4), marked with FIX below:

           $key = trim($keystr);
	    if (!array_key_exists($key, $atRulesMap)) continue; // FIX
            $parentAtRule = isset($atRulesMap[$key][$i])
                ? $atRulesMap[$key][$i] : $atRulesMap[$key][0];


Test script:
---------------
$parsed = new HTML_CSS();
$parsed-&gt;parseString('function whatever() {
	do_this();
}	');


Expected result:
----------------
No exception thrown.

Actual result:
--------------
Unknown error type: [8] Undefined index:
  Error in line 2023 of file /usr/lib/php/HTML/CSS.php

The exception happens on access to $atRulesMap[$key].</pre>]]></description>
      <dc:date>2009-08-21T18:57:38+00:00</dc:date>
      <dc:creator>brunobg &amp;#x61;&amp;#116; users &amp;#x64;&amp;#111;&amp;#x74; sf &amp;#x64;&amp;#111;&amp;#x74; net</dc:creator>
      <dc:subject>HTML_CSS Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/16356">
      <title>HTML_CSS: Feature/Change Request 16356 [Open] Order of items in css file not keept for at rules</title>
      <link>http://pear.php.net/bugs/16356</link>
      <content:encoded><![CDATA[<pre>HTML_CSS Feature/Change Request
Reported by torerikh
2009-06-21T17:48:12+00:00
PHP: 5.2.4 OS: Ubuntu Package Version: 1.5.3

Description:
------------
Currently the order of the elements in the css file is not 
always keept in the parsed result.

Given the following css:

h4 {color: blue }

@media print {
  body { font-size: 10pt }
}

h3 {color: blue }

@import &quot;foo.css&quot;;

h2 {color: blue }

@media screen {
  body { font-size: 10pt }
}

h1 {color: blue }

It is reported as 

@import
h4
@media print
@media screen
h3
h2
h1

if you investigate the _css. This is unfortunate as it makes it 
impossible to properly interpretate the CSS according to the 
CSS spec as order is important as some of the at rules should 
be ignored as they come too late in the css and the current 
parse result makes it impossible to handle such rules.

Expected result:
----------------
@import
h4
@media print
@media screen
h3
h2
h1

Actual result:
--------------
h4
@media print
h3
@import
h2
@media screen
h1</pre>]]></content:encoded>
      <description><![CDATA[<pre>HTML_CSS Feature/Change Request
Reported by torerikh
2009-06-21T17:48:12+00:00
PHP: 5.2.4 OS: Ubuntu Package Version: 1.5.3

Description:
------------
Currently the order of the elements in the css file is not 
always keept in the parsed result.

Given the following css:

h4 {color: blue }

@media print {
  body { font-size: 10pt }
}

h3 {color: blue }

@import &quot;foo.css&quot;;

h2 {color: blue }

@media screen {
  body { font-size: 10pt }
}

h1 {color: blue }

It is reported as 

@import
h4
@media print
@media screen
h3
h2
h1

if you investigate the _css. This is unfortunate as it makes it 
impossible to properly interpretate the CSS according to the 
CSS spec as order is important as some of the at rules should 
be ignored as they come too late in the css and the current 
parse result makes it impossible to handle such rules.

Expected result:
----------------
@import
h4
@media print
@media screen
h3
h2
h1

Actual result:
--------------
h4
@media print
h3
@import
h2
@media screen
h1</pre>]]></description>
      <dc:date>2009-06-21T17:48:12+00:00</dc:date>
      <dc:creator>tor-erik &amp;#x61;&amp;#116; web-amp &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>HTML_CSS Feature/Change Request</dc:subject>
    </item>
</rdf:RDF>
