This tutorial describes using a MySql database as the back-end data source, though the general principles in binding this data source to the form are the same despite which back-end LiveCycle-compliant database you choose to use. We will then add three rows into the database table, and we will create a simple PDF form in Designer that will include a drop-down list that is automatically pre-populated by this data source. To illustrate the process we will create a simple table in a MySql database. A common use of this concept is having a dropdown list in a dynamic PDF pre-populate with data from a database. An electronic form once wired to a back-end data source can be dynamically updated at any time. A form need not be created with one set of data and then left that way indefinitely. Using the :target attribute is also pretty awesome.One of the main benefits of electronic forms is their dynamic nature. I ought to see if I can adjust that current menu to do something useful without JS, using more of the CSS abilities (esp as you mention, current CSS offers a lot more than CSS in the heyday of IE6). I’ve made a decent JS’d dropdown menu but it was for my previous company where I couldn’t convince them to make anything work without JS- so it fails too much for my taste without JS. One of the reasons I started liking JS enhancements was because I started working with aria-ised widgets (where certain keystrokes are expected to do stuff: example of a tab-panel widget list of requirements, where basically having the aria-roles without the JS to backup the keystroke promises is bad) and so I’d been playing with menus, modal dialogs and the such (I’ve seen some pretty good CSS-only modal dialogs, but accessibility-wise if you’re using Assistive Technology they still have a lot of failings).īecause I’m a fan of progressive enhancement, I’ve been pushing my team to make even these types of widgets (tab panels, but also menu dropdowns etc) work at some level with good HTML, layer it on better with CSS, and finally let Javascript also do things like add in the roles (and use the roles as styling hooks in CSS) so that a user never gets something promising certain keystrokes unless JS is definitely there to do the job. (I was looking for a “traditional” text-based menu.) I’m never a fan of using images (or icons) in place of text (whether on a website or in flat pack instructions ), but once I got used to it, I quite liked that menu. I found that page a bit disconcerting at first glance, because there didn’t seem to be a navigation menu at all. My only concern with it is weather some touch-screen users may find the icons a bit cryptic since they don’t see the labels on hover. It appears fully tab navigable while being in vision and is fully responsive down to a silly small size without any media queries. I have a dummy example page with a new menu. The really sad thing here is that, as a regular keyboarder, I can confirm that is a vast improvement on many of the sites I visit. It’s not ideal only the focussed item from the drop-down appears, hovering in splendid isolation. When I ran into one which did, I hunted high and low for a solution, but the best I could do was to adapt the Sons of Ursidae menu. Most of my sites are very small and don’t require a drop-down menu. I, too, would love to see a solution to this. I don’t know of a selector that selects a parent of an element with focus, is there such a thing? I just can’t seem to find the right css selector to make this happen. I need the drop-down (a nested ul) to stay visible while its contents () are tabbed through and have focus. This is probably not the design I will use in terms of styling, it’s more about the functioning of it. But then it’s no big deal just to tap and see. I was experimenting with some “concept” menus systems. On the other hand, I have been thinking about giving the site a full code/style overhaul, but it seems a daunting task. Hiding the drop-downs with an off-set left:-999em instead of display:none, as per this, which claims to be Accessible, makes them “visible” to screen readers at least, which is better.īut what about seeing users who use tab navigation? They won’t see the drop-down links which have focus. I still have not come up with a proper solution to this, but have improved it slightly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |