When I click on web page the cursor start blinking and adjust its height according to table size. I want to stop that blinking. Is there any solution ?
Here’s the correct answer if not late though, It’s called caret browsing hit F7 to turn off simple as that
May be you have turned on your Caret Browsing, press f7 to get rid of it
I'm fairly sure there is no way to influence the blinking behaviour of the text cursor. This is entirely up to the browser and the operating system.
Here is a (very kludgy IMO) approach to hiding the text cursor altogether: Hide textfield blinking cursor
Related
I'm building a mobile app that lives inside of a UIWebView and is written in sencha.
Right now, I have a page that has a ext.list containing <textarea> element inside of the rows.
When the user clicks on the text area, the soft keyboard comes up and pushes the screen as expected. However, if you try to scroll the list while the keyboard is up, the list will dart all the way down to the bottom. At this point, you can try to scroll the list back up to see the <textarea> (keyboard still up), but whenever you're done scrolling and remove your finger it will immediately stick you down at the bottom of the list again.
Once you dismiss the soft keyboard, the problem goes away. We want scrolling with the keyboard up, unfortunately.
Things I've tried:
*Use the scrollstart event to unfocus the <textarea> and dismiss the keyboard when scrolling begins works, but like I said, we want scrolling with the keyboard up
*Put the <textarea> on a toolbar, or just plain fix it to the middle of the screen. It doesn't seem to care where the <textarea> is. The main problem seems to be the keyboard + scrolling interactions.
I've looked around for some time now and cannot find anything on this. It seems most people are complaining about Android, which I haven't even explored yet. I feel like this has got to be something people are incorporating into their apps, though (like a search that displays results while you type and you can browse those results), so I must just be missing something? Does Sencha 2 fix this?
Thanks in advance. I can post code and/or a demo as per request.
quick question regarding the TextEvent:LINK.
It stopped working recently when I switched my interface and I'm not quite sure why or how to fix it.
I have a movie clip which contains a text area and a scroll handler. 3 of these are added to my interface, although only 1 at a time is active in the display, depending on which tab you click.
All of that works fine, but once I change the chat object (textfield and scrollbar) in the display, it seems to stop working, and I'm not quite sure why. I'm not creating new instances all together, just adding and removing from a parent clip upon clicking different tabs.
Any idea what would be or could be causing this? As far as I can tell nothing is over or obstructing the clip containing the text field and scroll bar. The scroll bar actions work fine, which is next to the text field, however there seems to be no action going on as far as clicking links in the text field. I can select text in this text field as well, so I'm a bit confused :<
Thanks for your help.
Edit - Textfield is selectable, I know they need to be for the event to work.
I'm not entirely sure about the layout and the behavior of the project, but from my own bitter experience with TextEvents I learned that the less you mess around with the textfield, the better.
Maybe you should consider hiding the textfield instead of adding/removing it, i.e. changing the way the UI works without actually touching the affected elements in any way whatsoever.
If that's not possible, I'd try "rewriting" the text in the field and reattaching the event listener once the object is made visible again.
Hope you solve it quickly, texts are a pain in Flash.
Cocoa, Snow Leopard, Tiger compatibility needed.
I have a WebView containing some HTML. The HTML contains links, and is used mostly as a UI replacement for Cocoa.
Question: how do I prevent the 'hand' cursor from appearing when the mouse is moved over a link? For aesthetic reasons with this particular UI, I need it to stay as the arrow cursor at all times.
Thanks
Take a look at Cocoa WebView, WebKit - Prevent I-Beam cursor from showing over text?
They seemed to have a similar question, is that what you're asking?
EDIT: Haha sorry, I didn't realize that was you! Perhaps you could use that method for #a:hover ?
Take a look at http://trac.webkit.org/export/37902/trunk/WebCore/manual-tests/cursor.html it has a lot of different webkit cursors. The source code should be helpful as well
And from what I can tell cursor:default should make the arrow (from reading the source code)
When you touch an element, such as an edit box, in a web page on the iPad, it turns gray while you are touching it.
I have a table wrapped by a floating div. Instead of an individual data element or row going gray, the whole table (or its wrapping div) goes gray when a data element is touched. (The function of this table is an autocomplete pop-up)
Elsewhere in the site, I have a table in which only the touched data element goes gray.
I wondered if anyone could direct me to an explanation of the logic behind this graying on touch, so that we can code our table to give the desired behavior. Ideally, we'd like the row to highlight when it is touched.
In the alternative, if we could turn off this graying behaviour, that would be another option. We could then code the highlighting ourselves. Is there a way to turn off this behavior for particular html elements?
Thanks.
This author suggests a solution to remove the highlighting:
If for whatever reason you don't want some elements of your web site or application to be highlighted, simply add the following CSS rule to the corresponding elements.
-webkit-tap-highlight-color: rgba(0,0,0,0);
It won't disable the highlighting, but it will make it invisible (an opacity of zero).
I have not tested this, however.
I have discovered something about the "logic" behind the graying behavior. It seems that elements that have handlers such as onclick, onmousedown etc. exhibit the behavior and those without such handlers don't. A (somewhat tedious) workaround for us is to change the code of the autocomplete so that each row has its own onmousedown etc. handler rather than the wrapping div taking care of this.
Try styling the wrapper div with select:none;
That should turn it off, and then you could code the highlight onfocus yourself.
Most browsers actually do this, but it's a bit more noticeable on the iPad and other Apple touch products. It's really for usability purposes, so I would only recommend disabling it if it is causing problems like the one you mentioned. It serves to help the user know what they are clicking, and gives them a chance to move their finger away if they are on the wrong thing.
I like to display more info on certain keywords in a web page. I don't want to send the visitor to another page and I prefer to show the extra info on top of the current page.
The keywords are in an html list. It's basically a list of features and I want to offer more info about the features. So I have two ideas based on having 'More Info' or '?' hyperlinks.
The user hovers on the link and a popup window shows up with the info and goes away when they hover away.
They click on the link, a popup window with an 'X' shows up and they click on the X to close.
Which one offers a better friendlier user experience?
I like #1 because they don't have to click to open and click to close but the disadvantage is that windows might open inadvertently while they are mousing over the page.
Both are pretty annoying, but if I had to pick the lesser of two evils, I'd go with properly done mouseovers.
You can setup Javascript on the page to handle the accidental mouse over, and instead wait for a few seconds before displaying the popup window.
What would your users expect? Try not to break those expectations.
Maybe try a hallway usability study, grabbing a handful of users as they walk past the office, and just ask them to tell you what they would expect. :)
Asking Stack Overflow is a good idea too, but you won't get the advantage of context, which is very important with usability testing.
As a user myself, I find it annoying when I move a mouse and something pops up unexpectedly. Even with a javascript delay (which is better), I still think it's unexpected that something would pop up when I didn't explicitly click on it.
But, that might vary depending on the context of your application.
Personally, I'd go with the click option. There's a standard Way Things Work on the web which says that hovers are for information about the link itself and what action clicking on it will do ("See more comments", "Click for help", etc.), whereas clicking is what actually performs the action.
If you do decide to go with the hover option, make sure that you code it such that users can select the text in the popup. It's really annoying when you just want to copy some useful information somewhere and the GUI hides it before you can reach it.
Adding to what the others have said, I would also prefer the click option.
The problem I have with the hover option is that, and maybe this is just me, if the hoverable area is on the small side, I have a hard time keeping my mouse still enough to keep hovering. The cursor tends to move off the link in the middle of reading and my nice help text disappears.
People don't expect a pop-up on hover - I'd definitely go with the click.
Edit / addition: think about the website you visit every day - text and pictures are (generally) static, and hovering, at most, changes the colour or add underline to a link, or displays a small menu of clickable links.
When clicking on a link, you expect something to happen - a redirect to another page, a pop-up box with information, a form being submitted, etc.
I'm not saying this is the best way to do things, but it is the way 99% of the web works, and asking users to deal with pop-up boxes on hovers or the like is a good way to turn them away. I know I personally don't read any pages with double-underlined links; it's a good indication that an accidental break in scrolling to read the content might end up with my mouse over a link with an advertisement tied to it.
Having a little graphic beside clickable text, or otherwise denoting that clicking will lead to more information is a great way of providing contextual information without frustrating people. For most of the world, pop-ups without clicking still == advertisements or spyware.
Edit / clarification: I don't mean a pop-up in the new window sense, just a lightbox-style javascript pop-up. Don't take the user away from the page, and give them a very visible button to click to close the pop-up. I guess what I'm saying is that people don't expect something to happen without clicking, especially not if it's going to take up more space on the screen.
As a couple of additional precedents to consider, you might want to consider the functionality of the acronym and abbr HTML tags. Both allow you to provide extra information on a particular piece of text in the page, and both work on the "hover" principle.
Points to ponder:
If items are so dense that everywhere you move the mouse something pops up on hover then do NOT do hover!
Can you make hover show very brief info, and have click show more detail? This may be the best of both worlds if it works for you.
Can you have a dedicated box that displays info when you hover? This may be better than any pop-up. Opinions vary...
In the end it's what works for your app, from your users' point of view.