Skip to main content

JavaScript: Next Unique ID Function

Unique ID generation is used in JavaScript application in many places. For example giving the unique id to DOM element or may be using it to some data structure for storing in memory, where it can be use latter.

Most of the implementation I see is just defining the integer and increasing it on every call. But it is potentially candidate to integer overflow issue, which can cause errors in many edge case scenario.

var nextUid = (function(){
  var idCounter = 0; //integer counter
  return function (prefix) {
     //counter increment on every call, and it can run into integer overflow issue
     var id = ++idCounter; 
     return String(prefix == null ? '' : prefix) + id;

When I was reading through AngularJS source code, found this really good implementation of unique ID generation. Below is the extracted and updated version of the same, so you can use it independently.

 A consistent way of creating unique IDs in angular. The ID is a sequence of alpha numeric
 characters such as '012ABC'. The reason why we are not using simply a number counter is that
 the number string gets longer over time, and it can also overflow, where as the nextId
 will grow much slower, it is a string, and it will never overflow.
 @returns an unique alpha-numeric string
var nextUid = (function(){
  var uid = ['0','0','0'];
  return function() {
    var index = uid.length,

    while(index) {
      digit = uid[index].charCodeAt(0);
      if (digit == 57 /*'9'*/) {
        uid[index] = 'A';
        return uid.join('');
      if (digit == 90  /*'Z'*/) {
        uid[index] = 'a';
        return uid.join('');

      if (digit == 122 /*'z'*/) { 
        uid[index] = '0';
      } else {
        uid[index] = String.fromCharCode(digit + 1);
        return uid.join('');
    return uid.join('');

//output: "001", "002", "003", "008", "009", "00A", "00B", .., "01s", "01t", "01u", "01v" ..etc

Benefited of using this function is slow rate of increment, and you will never have to worry about the overflow issue. 


Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute.

Chromium issue for above behavior:

To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert".

<!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe>

Feature added: Block modal dialog inside a sandboxed iframe.

Feature working Demo page:

CSS Specificity

Many time different CSS rules overlap on one or more element. And some people always get confuse about, which rule will take higher priority then other and why? CSS Specificity is the answer of all these kind of questions.
As the name suggest, the CSS rule which is more specific to the element will take higher priority then other. Means something like “#some_id{}” will always take higher priority then “*{}” universal selector.  And if duplicate rules are define then the last rule will be applied to the element.

The following list of selectors is by increasing specificity:
Type selector (e.g., div) and pseudo-elements in selector (e.g., :after) Class selectors (e.g., .some_class), attributes selectors (e.g., [type=”radio”]) and pseudo-class selector (e.g., :hover) Id selectors (e.g., #some_id)

ID takes higher priority then Class, Type and Universal selector (Note: Universal selector has no effect on specificity, see below special conditions). 

If duplicate rules are given, then last…

JavaScript [ExtJs3]: EditorGridPanel Read-Only (dynamically)

Many time we face the scenerio where we have to make the editor grid read-only dynamically.

Ext.override(Ext.ux.grid.CheckColumn, { editable: true, onMouseDown: function (e, t) { if ( { e.stopEvent(); var me = this, grid = me.grid, view = grid.getView(), index = view.findRowIndex(t), colindex = view.findCellIndex(t), record =; if (!grid.isReadOnly && grid.colModel.isCellEditable(colindex, index)) { record.set(me.dataIndex, ![me.dataIndex]); } } } }); var grid = new Ext.grid.EditorGridPanel({ ... isReadOnly: true, //set to flag to make check column readonly ... }); //to make other column readonly grid.on('beforeedit', function () { return false; });