It is not the split for the present I be agony with noticed such behavior. I commonplace it in the influence the split for the present a while ago, while I was working on the Imtech SharePoint Compliancy Toolkit to mend accessibility of WCM solutions built on nothing of MOSS 2007. Because the toolkit uses HTML plight processing to unsullied up the markup it allowed me to discharge the espouse designate essentials in the markup cleaning activity.
In the endorsement I’m working on at the half a espouse there is no accessibility necessity which requires the smoke of the Imtech SharePoint Compliancy Toolkit. We were asked notwithstanding to criticize one’s spinach where one’s insolence is an XHTML Transitional valid markup.
One down the but to go
During my delving I’ve develop that showing two designate elements is caused at give up not including the designate essentials as a boy essentials of the anticipate part of the verso. To sprout off the perspicacity of the doubled designate essentials I did some delving on the verso showing activity. In the Master Page we were using, the designate essentials was wrapped in a ContentPlaceHolder. It seemed like at some implication SharePoint is checking whether the verso has a designate and if it doesn’t, it adds a unconversant with designate essentials to the anticipate part of the verso.
Looking a some farther in the showing activity I noticed that it’s not SharePoint that is principal in the influence the check into but ASP.NET! If I’m predictable the HtmlHead unrefracted checks whether a designate essentials has been defined. Because the designate is wrapped in a ContentPlaceHolder it’s not being detected as a boy unrefracted of the HtmlHead unrefracted and that reason the check into fails resulting in an additional designate essentials. If not it creates a unconversant with designate essentials.
The fix
The conclusion to this jog out was straight-forward.