innoq/simplete.obsolete

ROCAful autocompletion

simplete.obsolete's Issues

form elements inside search result list

Forms inside search results are not possible. The browser deletes nested forms.

<li data-value="info.pdf">
    <tt>info.pdf</tt>
    <small>PDF, 249 kB</small>
    <form action="http://google.com" method="get">
        <input name="q">
        <input type="submit">
    </form>
</li>
<li data-value="index.html">
    <tt>index.html</tt>
    <small>HTML, 43 kB</small>
    <form action="http://google.com" method="get">
        <input name="q">
        <input type="submit">
    </form>
</li>

accessibility (i.e. ARIA attributes)

Awesomplete might provide sufficient guidance

initial ajax request should be optional, if the search field is active or empty

minLength option

cf. http://api.jqueryui.com/autocomplete/#option-minLength

retain license info during minification

• add license info to source
• adjust minification process to retain license info

debounce

this might be an incentive to switch to CommonJS in order to use https://github.com/FND/uitil

documentation

• why?
• distinction suggestions vs. results (the former prepopulate the field's value, for the latter values don't matter)
• default results (i.e. if value.length === 0 - e.g. useful for user's favorites, recent history etc.)
• data-formaction, data-formmethod, data-scope
• DOM structure (e.g. .pending, placement of results container)
• expected server response
• HTML might also be rendered client-side, independently (requires additional hook?)
• JavaScript API (both wrapper function and constructor)
• debounce bonus

prefetching

it might be useful to prefetch default results to avoid any lag when the user first focuses the input field

browser compatibility

while Simplete should Just Work on reasonably modern browsers, we should check (including subtle details like de27cc8) and mention as much in the README

• IE versions
• mobile/touch devices

avoid jQuery dependency

would be nice to go pure-DOM, or at least ensure Simplete works with Zepto instead of requiring jQuery

we should probably have tests first though (cf. #11)

unit tests

linting, style compliance

• JSLint / JSHint / ESLint
• JSCS

@bengillies suggested Airbnb's presets might be a reasonable start

Custom Headers

Hey @FND 😄 For our current project we (@mjansing & me) added the ability to render a page without its layout by providing an HTTP header called 'layout' with the value 'false'. We want to use it in both simplete as well as pjax. We therefore need the ability to set custom headers in the HTTP call done by simplete. Are you ok with that? If so, we will implement it 😄

improve demo

current behavior seems unpredictable and thus confusing, as there's no obvious connection between input and results

might use Pretender or Stubby to filter HTML client-side after requesting a static page from the server

while we're at it, an omnibox might make for a better demo, combining results from various categories (e.g. users, wiki pages etc.)

also, an incremental tokenization demo might be convincing: pa[sta|rmesan] [AND|OR] to[matos|...] [AND|OR] [lemon|...]