I haven't been able to find a tutorial for developers, just endless tutorials showing users how to turn the feature on via a Google search. Does anyone care to share how this was achieved? Here is a small example of my code..no autofill (yet). I do have my contact card filled out and the option turned on.
<div style='display:block;'> <
<input name='first_name' id='firstName' type='text' />
</div>
Works if you wrap it with form tags. It's maddening that there isn't any documentation around this feature.
Related
I've been playing with the different types in html for the app I'm making. However, I'm making this app for touch screen computers so I a wondering if the 'stepper' that appears when it is either a type="time" or type="date" can be made larger so it is easier to press. Right now it is quite hard with big fingers and I can't find anything on google.
the html looks like this
<input type='time' value='' />
And a picture of what it ends up looking like.
Any help would be great!
I have an ASP.NET webpage that is rendering many (~3000) <input type="text"> textboxes on a single page (that are client-side only, i.e. do not need to postback). In Chrome, if these inputs are wrapped in <form> tags, Chrome will hang while I'm typing into the textboxes. (Duration is proportianal to how many textboxes are on the page). Firefox and IE do not have these problems.
You can view samples of my pages in the following links:
Slow page (with <form>): http://jsfiddle.net/ZXcMs/
Fast page (without <form>): http://jsfiddle.net/5V74U/1/
My questions:
Why is this? What exactly does <form> mean to a web browser?
My ASP.NET project requires the use of a <form> tag. How else can my site be made compatible with Chrome?
Nathan I just try the pages that you give and they not hung at all to me. I use the Chrome version 19.0.1055.1
Now what I remember is that I have a similar issue and was because of an extension !
Google Chrome is still developing and go from version 1 to 19 in one day :) and extensions are not so good tested with this version change. So extension that have been written just before some months maybe have problems now.
Disable all extensions to see if the problem goes away, and then if it does, just locate the one that have the issue.
Can anyone explain why my input type="file" is greyed out in IE8 but not IE7. It's still usable, but you can't actually type in the box any more.
<INPUT id="fil1" type="file" size="44" name="fil1" runat="server">
IE7:
IE8:
<input type='file'> is treated as a special case input field in all browsers. It looks different in pretty much every browser, and it can't easily be styled using CSS.
The reason for this is that the browsers consider it to have security issues, for example, where users may upload files without realising it. They therefore enforce a standard look and feel for it, so that the field will always be recognised for what it is. They also prevent CSS and Javascript from having access to the field so that they cannot modify the how it looks or alter the value of it.
In the case of IE8, the browser developers have decided that the only way the user should be allowed to access the field is via the file selector button. This is a concious decision by the IE developers to increase security. There's nothing you can do about it.
For the sake of curiosity, you should try seeing how <input type='field'> is rendered in other browsers - Firefox, Safari, Chrome, Opera... you'll be surprised by how different they all are in how they render this. It's probably the single most inconsitently rendered element.
Because the textbox is readonly; which is the expected behaviour. You can select a file using the Browse button.
Typing is not an option, since the file is on the users pc and the webpage cannot directly access those files.
i am using the lightbox2 module in my drupal site.
i would like to be able to trigger the lightbox on content that lies withing the same page.
something like this:
<a rel="lightbox" href="#">Show content in light box</a>
<div id="content_to_show">the content i want to show in my light box</div>
cant figure out a way to do that.
any help ?
well after searching around, i have came to the conclusion that lightbox is not the proper plug in to use.
instead i am using the colorbox plugin at http://colorpowered.com/colorbox/ which has this capability integrated, and simple to use.
Hi fellow Umbraco users,
I'm currently building my first umbraco website and since I'm completely new to umbraco I've already ran into a problem which I'm sure is pretty straight-forward to do.
That said, I'm by no means a beginner when it comes to building sites that run on a (open source) CMS as I've been using Joomla! since it was called Mambo.
Anyway, the site I'm building is here: my site
What I want to do is to have some content in the white box that changes when you mouseover/hover one of the menu items. Also that content has to stay "active" when you've clicked on a link (i.e. if you click on "Profile" I need to highlight the Profile menu item with the gray color and the white boxs content needs to be what would be related to the Profile menu item.
How do I go about this? What would be the best practice when it comes to showing multiple content on a site? I've watched the video about multiple Content Place Holders, but I never really got it to work. I can't get a page to display in the NavigationPlaceHolder (the placeholder I put in the white box), but thats because the actual page is Frontpage.aspx and not WhateverIsInThenavigationPlaceHolder.aspx. If I go to the mysite.dk/WhateverIsInTheNavigationPlaceHolder.aspx it shows up fine.
What have I missed here? :)
Thanks in advance! If my question is not clear in some ways, please tell me and I will try to explain it better.
All the best,
Bo
It's a little confusing what you're asking with seeing your implementation, but here is a shot at what I might do:
Rather than trying to do this through the templating system, I'm pretty sure you want to create a user control to add to your page template. (Add it in the template as a macro.) I would use and XSLT control here with this as the basic output:
<xsl:variable name="subContentNodes" select="$currentPage/node[#nodeTypeAlias='yourContentNodeType']">
<ul id="content-items-nav">
<xsl:for-each select="$subContentNodes">
<li><xsl:value-of select="data[#alias='pageBody']" disable-output-escaping="yes" /></li>
</xsl:for-each>
</ul>
and then later
<div id="content-items">
<xsl:for-each select="$subContentNodes">
<div id="subnode-{#id}"><xsl:value-of select="data[#alias='pageBody']" disable-output-escaping="yes" /></div>
</xsl:for-each>
</div>
It looks like you're already including jQuery on your page, so I would then add a script to handle the clicking:
$("#content-items-nav a").bind("click", function(e) {
e.preventDefault();
var contentDiv = $(this).attr('href');
$("#content-items div").hide();
$(contentDiv).show();
$(this).addClass("active");
});
Hope that helps you some. I found there is quite a learning curve to umbraco, but it is quite powerful when you get into it.
(Note: I haven't syntax checked any of the code)