Tag library 'div' hook

Question

Well, 'div' is not corrupt, but the application programming related to customization of Tag libraries is corrupt.
What is happening:
When Dreamweaver CC is installed, and when it opens fresh html files, it makes a mess of line breaks and indents in the text layout of the code. Using the menu item Commands / Apply source formatting also makes a mess, This menu command mess is a slight improvement over the horrendous mess that Dreamweaver CC makes of code when it opens and when it periodically 'refreshes' the files that it trashes. However, the code is not usable, as with more advanced css and html technique, the code becomes unreadable for Chrome, Internet Explorer, Safari, and presumably all browsers.
DW's mess described:
All indents are as spaces, making manual clean-up repetitive, necessary and extremely tedious.
The head and body tags are indented far inside their content, and that content is also erratically indented.
The use of Tag library editor would seem the expected user path, in seeking a user resolution, and perhaps in defining a programmatic intervention.
All tags are trashed, put going to the heart of the html cascade, we start with the p tag: e.g., p tag in Tag libraries defaults as
Line breaks: before and after tag
Contents: formatted and indented
Case: default
We try numerous combinations of p tag settings in the noted dialog interface.
The p tag settings do not appear to effect the mess. Dreamweaver, ignores default and manual settings, sometimes shuffling the mess a little, but minor shuffling only occurring twice, and without any tag block line break changes.
Perhaps, for a given instance of Dreamweaver installation, within a given simple document's system interface, Dreamweaver settings may reveal something called a 'performance hook' by application programmers. Perhaps we can isolate a hook that is useful for the Adobe support; support that lacking professional attention has maintained Dreamweaver as a failed application for over a year (since October 2012) on my Windows desktop. We move next to the div tag.
Manual intervention 'exposes bad behavior of div tag' hook:
Our simple document layout is... simple. Deploying doctypes for both html5 and xhtml transitional and deploying internal and external style methods, with the same code trashing result, we correctly layout tags as HEAD, BODY, DIV and P. Beginning with the p tag, various tag library settings are applied to determine effect on Apply source formatting command. Various p tag settings have no effect, and p is returned to its DW default setting, as noted above. The following div tag settings disable Apply source formatting command's code trashing specifically of line indents.
Line breaks: before and after tag
Contents: formatted but not indented
Case: default
Unfortunately, with this setting, line breaks between only some tags are maintained during Dreamweaver's auto code trashing (e.g., between closing head and opening body tag): sometimes when Dreamweaver does it's auto (or manual) trashing, these specific line breaks, between block tags, are not preserved. However, with this Tag library setting for the div tag using the noted basic cascade, all tag indents are ignored. But only when code is manually kept against left margin, without any indentation. And, ONLY WITH DIV TAG HOLDING THESE PARTICULAR SETTINGS, FOR THIS PARTICULAR DOCUMENT!
FLAT CODE is preferable to the bigger mess that Dreamweaver routinely imposes as it auto trashes code. Also, allowing any left margin indentation worsens Dreamweaver's code trashing... so, given Dreamweaver's chaotic destructiveness, I don't know if it is correct to imply any significance to my manual Tag library settings management, but it is clear that Dreamweaver is unable to correct the mess it makes, using the manual Apply source formatting command. And this is the first 'performance hook' that has been defined for my desktop in over 400 days. But setting div tag in this way is the only way to stop Dreamweaver trashing code layout line indents (trashing that occurs both during Dreamweaver automatic actions and with user menu action, for the specific noted html layout - a layout that is far too basic to be useful for 99.9% of design work). But only for a given instance of Dreamweaver installation for a given OS installation, and not across OS installations, or with any other file than the file (or files, in relational assessment) targeted for our 'hook' presentation analysis.
Conclusion:
Dreamweaver trashes code layout every time the application applies code formatting (e.g., opening new documents from other sources, applying menu commands, etc.). That is, all user code layout will be trashed by Dreamweaver. However, a specific div tag setting in Tag library editor may maintain a single instance for manual correction of Dreamweaver code trashing, when basic page layout is used with div in the noted cascade, and with div settings manually corrected as noted. This is a hopelessly unacceptable condition that the Dreamweaver application imposes on design work for my Windows 8.1 operating system. Professional designers of global significance and stature using many variants of Mac and PC systems have warned me not to use Dreamweaver, recommending numerous alternatives. I am taking the position that Adobe retains a shred of marketplace survivability, and therefore will promptly fix minor problems when I bring them to Adobe's attention.
IMPORTANT:
Obviously, this is not acceptable application performance. Is support available to Adobe that will now, immediately repair the Dreamweaver application that I use as a paid subscription to eliminate systematic code trashing?

Answer 1

I figured it out. Under the Configuration/TagLibraries,
create a CrossTagAttr folder and stick a .vtm file in it. In the
.vtm file, use the <crosstag_attributes> tag and its
children. See Configuration/TagLibraries/CrossTagAttr/Spry/Spry.vtm
for an example.