Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

I 'hear' JS again, with XAJAX

Featured Replies

Just a quick heads-up to anyone interested in really simple AJAX...

 

Search Google for 'xajax'. We started a couple of projects using it last year, and it has made a WHOLE HEAP of lovliness possible, including an interactive Google Maps interface for a client of ours.

 

Not much brainwork either... very simple constructs... imagine being able to have one single page loaded in a browser, and let client side/server side scripts interact to manipulate data on-the-page?

 

For instance, having the results of a page form DYNAMICALLY call from a database and insert the result into the page, without a submit, without a reload? Yep... this is AJAX folks. Being using the AJAX power for a while, but XAJAX really has sped up development here.

 

One great usage we're currently developing with XAJAX is a shopping cart system which allows the shopping cart to auto-update on the page, on the fly, when selections/options are made. Even the shipping charge is calculated on the fly. All this is done without a submit, without a reload.

 

Sounds simple? Well, yeah... the *effect* is simple, but the actual speed which this is achieved is breathtaking.

 

Havent' had so much fun since I coded my first game on the ZX81 ;)

Oh wow... that definitely looks fascinating. What does the new "X" stand for?

  • Author
How is its accessibility?

 

As with most scripts, you can make it as accessibility-compliant or not, depending on use.

 

Because it's JS based, any changes to elements are *not* seen in the source code, therefore it is wise to populate elements in the body, and only *change* them when required.

 

This can also cause havoc if the browser back button is used!

 

Another caveat is when writing for assistive technologies in mind, such as braille readers etc.

 

As with all these things, it's a good thing to write your pages *without* bells and whistles and make sure they are as compliant as you want them... THEN determine how to make them all-singing, all-dancing, and remain as compliant as possible.

 

XAJAX is unfortunately no more accessibility friendly than any DOM scripting exercise, so you need to 'design' your pages very well to enable them to be universal.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.