siteroller / domparser Goto Github PK

Should properties be included in the original regex instead of its own function?

DOcs has no description of how root and up is handled.

Constructor should default to 'auto' for absolute URLs

Mootools style!

allow get() to return an object.

$response   => auto/string/array/object
    'auto' - if only one item, return as string. Else return array.
    'string' - '<div>A</div><div>B</div>'
    'array' - array([0]=>'<div>A</div>', [1]=>'<div>B</div>')
    'object'

"set property and styles selection not implemented".
Is this correct? If so, remove from docs for now, and add to feature requests.

Logic for creating divs

The current names will confuse devs to no end!

$matches, $matche, $match ?!

Listed as 'fixed' by ????. Was it? Check in getter and setter.

Store properties with quotes
And / Or include into original regex

Should get allow for selection of styles ?

Local URLs should default to using file_get_contents instead of using curl.

If string is > 10 char it should not be checked against the array.
Check array to lower
get(div[id=abc], div[id=def], 'array');
The first two args are > 10, skip.

If there is one closing div to few, all content is not returned correctly.

Not sure why, filing this based on memory. I recall it being a trivial fix.

:root should not include doctype or other comments

The following is currently unhandled:
<p bold text </b</p This is even valid HTML (but not valid XHTML)
<!-- abcd-- >

Should have El Array + Prop Array in get().

(instead of merge?)
Array - unique at end of get/set

Copied from bug report. Look into what it might mean :(

Add option to NOT sort the queue, modify code to make it work

Unable to handle ids that have a dash in them ("#div-1")

Are excluded tags handled correctly?
Bug reports require this to be confirmed!

All non standard tags are put into 'comments', they should be subdivided appropriately.

When content is added to a self-closed div tag, it should be converted to a proper closing tag.

<p id="myP" />
set->(..content..)
return: <p id="myP">..content..</p>  

set tags should offer both opening and closing tags.

Fix all over.
This will also fix :sort

Document and release code where applicable.
Using:

1. Current regex
2. Fancy regex.
3. A series of splits
4. The Pear function
5. The competing class

Allow for nested divs in queue

Make sure all incoming pair[0]s are moved to lowercase

Not all selectors are handled, especially the "odd" ones.
I hope to fill in a list as part of this bug report, and remove them as they are added

change index back to numbers instead of using the eNumber variable.

This was a regression involved in some earlier versions of various features, but is not needed.

[get & set]? constructor should be able to accept arguments that are not encapsulated within an array.