Inclusions <?php ?> Do not pass validation. Perhaps this is normal, but unpleasant. Check on the validity of the page can be done in two ways. Sending the page address and sending the page code. It is clear that when sending the page address there are no problems with validation. Because the validator simply does not see PHP inclusions. But who is like, but for me it is rather inconvenient to catch errors from the resource already posted on the site or on the local host. It is much more convenient to do this directly from the editor. This is where the problem of finding non-existent errors arises. The question is the following, maybe I don’t know what, and you can set up an editor, for example, “Dreamweaver”, so that it gives the page already processed by the server to the validator, or you can specify something directly on the page for the validator so that it doesn’t swore? Or even just wait and the consortium will solve this problem?
SLy_huh
1.295 2 14
Alexander Alexander
one one
- oneIs Dreamweaver not for client side? - SLy_huh
- oneAnd just do not pay attention to them? You know that these are not errors and there will not be these tags on the client, there will be only html code - Vadim Leshkevich
- Like, yes. But there is one moment. The validator takes the tags quite seriously, and already inside the inclusion starts to find errors, for example an unclosed tag, etc. If the inclusion is extensive, it confuses and there is a loss of time. In addition, it is possible to skip the real error and, as a consequence, the loss of cross-browser compatibility. That is, in your browser everything is fine, but in Safari everything will skew, for example. - Alexander
- Surely this problem is solved by a consortium. Here are just to know how. There clearly need a specialist close to their circles, who could give a detailed answer. - Alexander
- And Dreamweaver sends the page code raw by the server. Maybe something in the tinctures wrong? - Alexander
|