v1.0.0-beta.4 'antimony-antelope' Released!

Download Instructions: https://github.com/driftyco/ionic#quick-start

Bug Fixes

  • .pane: Remove overflow:hidden from .pane,.view (64f0030b)
  • .tabs-icon-*: only work on directly descendant tabs (77f26831, closes #1261)
  • bar: properly align titles if switching to view with no buttons (ade143ed, closes #1242)
  • collectionRepeat: correctly save user scroll position on back (0a640758)
  • ionItem: fix error when repeating (f370db45)
  • ionSlideBox:
    • fix disable-scroll attr, deprecate in favor of $ionicSlideBoxDelegate.enableSlide(true/false) (1bdb5e8d, closes #1113)
    • prevent NPE during drag (920dc59d, closes #1240)
  • modal: Remove modal flicker, closes #1150 (d2ebed84)
  • scrollView: recalculate size on mousewheel scroll (89a9ed15)
  • select: Select options w/ mouse events, closes #1251 (e3306293)
  • tap: input[file] clicks within ion-content, closes #1237 (05a6d7cc)
  • toggle: Right side padding for item-complex, closes #1091 (45106a6a)
  • transitions: Disable transitions on Android 2, closes #780 (9c58d47b)
  • viewport:
    • Auto update viewport tag (5f8e9040)
    • Remove height value on iOS browser (0ad10ede)


  • $ionicLoading: on android, no back button action while loading (fc8711c7, closes #1273)
  • $ionicModal: close on backdrop click on desktop/tablet (554c4398, closes #1087)
  • ionNavBar: allow navbar inside ion-view to transition whole bar (42177c3b, closes #1232)
  • sideMenu: make android back button close side menu (10103559, closes #1264)

This topic is now pinned. It will appear at the top of its category until it is either unpinned by a moderator, or the Clear Pin button is pressed.

FYI, beta v3 and v4 ionic.css = ionic.min.css (aka not minimised)

Hi, I tried the last beta, but my simple view is not displayed because I’ve this error:

"Error: onMouseWheel is not defined

My template view:

<ion-view title="Login">
    <ion-content scroll="false">
      <div class="list">
        <label class="item item-input">
          <span class="input-label">Username</span>
          <input type="text" ng-model="user.username" />
        <label class="item item-input">
          <span class="input-label">Password</span>
          <input type="password" ng-model="user.password" />
      <div class="padding">
        <button class="button button-block button-positive" ng-click="LogIn(user)">
        <p class="text-center">


Hi @biapar, I’m not sure why that would happen. What browser/platform are you getting this problem on?

Fixed, thanks! We temporarily disabled css minification earlier due to an npm problem, and forgot to restore it.

How in the world do you upgrade a project from a previous version? I’ve done it before but cannot remember what I did. This should be easy and should be in the release notes, please.

@andy: I use Firefox 29v.

Just replace lib/css/ionic.css, lib/fonts/*, lib/js/ionic.bundle.js in your project for the new ones.

Then, test your app, and if there are something wrong, just take a look at http://ionicframework.com/docs/api/ and solve it. Should be a breeze

  1. Download (Ionic Package: 1.0.0-beta.4 Antimony Antelope):

  2. Delete the old css, fonts, js folders from “YourProjectFolder/www/lib/” and paste the new one

  3. If you use gulp you can find the scss here “https://github.com/driftyco/ionic-bower” do the same like in 2 with the scss than open you project folder with the terminal and type gulp


PS: If there are code changes you must look in the forum

1 Like

Hi, was having the following error after upgrade

Error: onMouseWheel is not defined

Firefox 26

OS Linux mint

Upgrade method
Unpackage and overwrite lib/ionic/*

i dont know, i test it now, the error only fires up on mozilla, try chrome…

its a bug?

onMouseWheel is not defined — Getting this in FireFox(latest) as well.

Fixed in the nightly builds. There was a jshint error with defining a function inside an if-block that wasn’t fixed, which I guess Firefox really hates.

We definitely need to add more browsers to our unit test suite so this never happens again.

Yes but if firefox (desktop) decides to explode by some reason, that shouldn’t be a priority when the framework is mobile oriented!

it seems that the old keyboard issue(the keyboard is covering up the input fields in a form when typing and you cannot scroll up) is back in beta4. beta3 didn’t have this issue. does anyone have this issue in beta4?

There’s another issue, when entering text into a text field, the text fields didn’t get updated until you tap on somewhere else. e.g. you type"abcd" into a text field. when you close the keyboard, the text field is still blank. I have to tap on some other field in order make “abcd” to show up on the text field that I was trying enter.

I am testing on my nexus4 w/4.4 and I set to fullscreen in the config.xml

1 Like


While that may be their focus now lets keep in mind that desktop browser support is still nearly half the market share.

Saying desktop browsers aren’t a priority makes a lot of assumptions about how a developer may actually use the framework too. For example ---- I am currently building a web app with Ionic and when it’s done I will use build scripts to tailor the experience for Android/iOS apps ---- this allows me to keep a unified code-base, which is very, very powerful.