#KartikPrabhubut php-mf2 also does class subsitutions
#ZegnatI think most people are passing in an HTML string and getting parsed mf2 out, so they can’t run into this.
#ZegnatBut if you pass in a DOMDocument to the PHP parser, and then try to use the DOMDocument object again after parsing these same issues might occur.
#KartikPrabhuyeah that seems reasonable. I haven't run into this in practice either
#ZegnatWould need to test. Filing bug. Not something I want to start testing past 11pm :P
#gRegorLoveConfirmed if you pass in a DOMDocument to php-mf2 it's changed after parsing.
#KartikPrabhuok. don't know if that is good or bad yet. In php-mf2 it might not be an issue since the whole DOM is changed to mf2
#gRegorLoveIncluding the children, though, so a second pass shouldn't (I think) cause problems
#KartikPrabhuI might have preemptively overoptimised :|
#gRegorLoveSounds like php-mf2 should definitely copy the DOMDocument and work on that
#KartikPrabhuright if the backcompat rule that "ignore mf1 if mf2 is present" is used then it won't be an issue in second pass
#KartikPrabhuI am also in favour of not changing things the user passes in explicitly
#KartikPrabhuin mf2py that might need some funny code since BeautifulSoup does not support "deepcopy" i.e. making a separate duplicate
#gRegorLoveYeah, I'm wondering if PHP is similar. I wouldn't have expected it to change the input DOMDocument since it's not by reference, but maybe it's a special case
#KartikPrabhuI suspect it is by reference since it is some object or something