General

Re: Unexpected CSS Formatting

dapklp — Wed, 19 Jun 2019 15:18:01 GMT

My apologies for the delay in finishing out this post, but as it turns out, the CSS error actually never went away. I would do Design Checker and Preview after each change to copy over parts of the Printing View and InfoPath told me No Problem. But when I went to publish the form, there it was again. I think there is one little unclosed (“) or something somewhere that gets copied over and blows the whole thing apart. I tried copying from bottom up an from top down and no such luck. I removed the view and after several other errors with data imports I had since removed, finally got it to publish like a nice little Web form (without the table). Then I rebuilt the the page from scratch – at least I could reference the other copy for cell sizes, etc. I'm pleased to say the rebuild from scratch worked. I still do not have a solution to address the CSS error other than wipe it out and start over. There was something, somewhere in the table that when copied, kept the issue alive.

Re: Unexpected CSS Formatting

dapklp — Thu, 02 May 2019 13:21:27 GMT

Yes, my apologies for the brevity of my initial question - this was from Design Checker. As Hilary stated, I located the offending view by systematically eliminating items/views until only the offender remained (along with the error). I then created another form without the offending view and systematically copied over parts of the table and then performed Design checker. Oddly enough, after copying over every part of the table a piece at a time, the new form did not have the CSS error, so I apologize, but I cannot offer any insight as to exactly what caused it.

One thing I do need to keep in mind though is that in addition to performing Design Checker after each revision session, I also Preview the form. One time I saved the form and only performed Design Checker and then when I went to Preview it, InfoPath told me there was a catastrophic error - Too Bad Sucka (DAP paraphrased). I don't know why because Design Checker told me everything was copasetic, but that copy of the design file was no longer viable.

Re: Unexpected CSS Formatting

Hilary Stoupa — Fri, 26 Apr 2019 19:50:01 GMT

Just updating this thread from our email conversation - it was a specific view in the form, which your detective work had already uncovered. I verified that once everything except the layout table was removed, the view would pass design checker - which is not terribly helpful. I don't know of a tool that would check the validity of the CSS in the XSL - and the file is way too long to try to manually scan for issues.

Re: Unexpected CSS Formatting

Hilary Stoupa — Fri, 26 Apr 2019 19:01:36 GMT

Ok - so this is in the Design Checker? Or when you try to publish the form? A bit more info would be helpful. :)

Unexpected CSS Formatting

dapklp — Fri, 26 Apr 2019 18:55:20 GMT

"Unterminated quotes encountered in CSS string." - but no assistance on locating it to correct it (whatever it is). Any ideas are welcome.