So Tridion UI/XPM/SiteEdit default TBBs output a
<span> tag around each Component Presentation and Field changing the DOM and sometimes conflicting with your site's styles. So a project has been created (https://github.com/TridionPractice/tridion-practice/wiki/TridionUI2012FunctionsForUseInHtmlTemplates) that proves these are not necessary. It looks like you can simply print the SiteEdit markup in front of the editable field (btw, very cool).
So why aren't the default functions
@@RenderComponentField(...)@@ doing that straight out of the box?
I thought that maybe backwards compatibility could be one reason, but upon second thought this doesn't make sense because if you upgraded you'd still need to swap out your TBBs and republish your pages. So you'd be good to go.
I'm assumming there had to be some other architectural reason(s) why the
<span> tags were needed and I'm curious what that scenario is.