I am noticing this attribute added to HTML source, I can't find any information about it.
It starts in the head tag:
<html wtx-context="8F1EE800-7352-408E-AC70-5297G5FD3F25">
It also appears in form elements and inputs.
Any information would be useful, such it's purpose and what it is thats inserting it and why?
Sorry, late answer. I browsed the web for this question too but didn't find anything useful.
It happens that I installed bitdefender a couple of days ago and guess what ? It's the culprit. Even if its extension is disabled, it adds this weird attribute. I completely uninstalled the plugin (not the AV) from my browser (chrome) and that's it.
Im using primefaces/ckeditor and experiencing some issues with performance on large amounts of text under IE11 (this doesnt happen under Firefox)
I am wanting to test the impact of removing some plugins/extensions - but cant find a list of whats installed by default.
I suspect the list is defined under -
https://github.com/primefaces-extensions/resources-ckeditor/tree/master/src/main/resources/META-INF/resources/primefaces-extensions/ckeditor/plugins
Can anyone confirm this?
I don’t understand why this was elected to close – but the answer can be found under build config -
https://github.com/primefaces-extensions/resources-ckeditor/blob/master/src/main/resources/META-INF/resources/primefaces-extensions/ckeditor/build-config.js
You can see the selected plugins if you follow the link listed under build-config -
http://ckeditor.com/builder/e6b8a045f8f984a69463975ca3e6524a
Does anybody know anything about chrome.experimental.sidebar namespace? Is it still available? Is it going to be removed? Anything?
It's not available in the Google Chrome Extensions documentation anymore.
Do you know anything about availability of sidebars in Google Chrome?
You can see all relevant information in the corresponding Chrome bug. To quote comment 41:
The sidebar's on ice for now. We're going to go through an API
prioritization exercise near the end of the year to figure out what's
important for 2012, so there's some chance it could resurface. I'd put
the probability pretty low though.
And comment 42 clarifies that a sidebar API doesn't seem to be the top priority right now but it might still get finished later. Or, what sounds more likely judging by comment 50, this functionality will be morphed into a more generic API.
I'm trying to track down two missing closing div tags in a 2500 line html document, obviously I'm doing this manually but I remember that Visual Studio helpfully highlights the closing tag of the currently selected tag.
Don't have VS available but wondered if anyone knew of similarly helpful tool for this kind of task?
//update
Should probably say that I'm already using a validator and an editor with syntax highlighting - mainly I'm curious to find out what others use.
I like Firefox's add-on HTML Validator:
https://addons.mozilla.org/en-US/firefox/addon/html-validator/
It works and you never have to leave your browser or copy/paste markup.
W3C also has a great validation service.
http://validator.w3.org/
I absolutely love Geany. Haven't used it in a few months (forced to work on a .net project), but IIRC, it will do exactly what you need.
http://www.geany.org/
An interesting issue which I've googled and can find absolutely no reference too, perhaps because I'm too vague on the cause myself.
I have a simple jsp page that is run from a struts 2 action. It' fairly javascript heavy, but its an internal app on my company's intranet so thats not a great problem.
All seems normal so far, right? but interestingly, the last few tags on this page fail to render. This is true for all browsers I've tried it in (IE, FF, Chrome).
What I mean by not rendering is that they simply don't exist when you view the source! whats worse, in IE, half a tag declaration is actually printed as text at the bottom of the page. All very odd.
But what makes it even stranger, if I put a few <br /> tags after the </html> tag, then all browsers render down past the </html> tag, but still cut off the last few <br />'s.
Has anyone ever heard of anything like this? I don't even know where to start troubleshooting! I know my description is vague but that's only because I'm a bit vague on it myself.
If 'View Source' does not show you the tags then it is not a rendering problem, but a server or network problem, as the content is not being delivered to the browser.
It sounds like a buffer flush problem to me. Have you got any filters that might be buffering the html before it gets to the browser?
Sounds like you have an unclosed quotation mark somewhere. Or something like that. Stuff like that can mess up even the source view as some browsers don't show the exact bytestream they received in the socket in source view (I know for a fact that IE used to do this). Try doing a GET with wget or a telnet client or something similar and see what happens.
We should see the code of your jsp to answer. I suspect there is an unclosed tag or a an unclosed quotation mark of an attribute - as DrJokepu said - in the jsp.
That is the first time I have heard that IE is behaving the same way as the other browsers; by accident...
But seriously, is the html error-free?
I recommend using the html validator extension for Firefox to show you if the html is producing any errors or warnings.
There has to be an error somewhere, but without the code it is impossible to say what it is.
I had a problem some time back with a web-site that was getting 'cut-off' and similarly, I solved the problem with a quick hack but never a proper solution. What it came down to for me was that the web server seemed to require the content-length of the page for it to render properly. When I buffered the output and added the content length, the page would load in full. Different technology though - this was an application built on Perl CGI running on Apache 2.2.
Thanks for the assistance all, but unfortunately none of these seemed to help. I've found a hacky way around it and since its not a critical app, It'll just have to do.
thanks again