3 ms·

How nice of you to hijack the back-button (to return to HN after some sample queries) despite that being how myself & others found this in the first place. I w

How nice of you to hijack the back-button (to return to HN after some sample queries) despite that being how myself & others found this in the first place. I was really liking the product up until that point.

dewey 6y ago
There are nicer ways to say that, it might just be a tiny bug on a brand new project that someone is sharing.
bluestreak 6y ago
someone already brought this up, there is rationale for it at bottom of this thread
- shreddit 6y ago
  well, ‘breaking’ basic browser functionality because it breaks the design of your page is not really something i would call rational... As stated some comments below, the code literally says ‘disable back button’
  - bluestreak 6y ago
    We will find a way to fix this and have grid scroll without problems at the same time. This is not a dedicated website. This is exactly the same web console that is packages with our free product. It wasn't meant to run on the internet and confuse people. Sorry
santafen 6y ago
As someone else pointed out, and a QuestDB engineer responded, it’s been noted and an issue has been created for it. 5e reasoning for it was actually solid.
MarcellusDrum 6y ago
Yeah an extremely pathetic move.
- sirffuzzylogik 6y ago
  Sorry for the frustration guys, this was not meant to be "something to lock people in". The rationale for doing this was to prevent macOS users from going back when scrolling the grid horizontally. I submitted a PR to remove this for now, in the future, we will implement a better solution that does not mess with the History API.
  - thoraway1010 6y ago
    I'd keep it, I hate working on boxes and when I move left outside box I go back. THAT is the annoyance especially if I'm doing entry work. I'd always wondered WHY this happened.
    - sirffuzzylogik 6y ago
      I have mixed feelings about this feature actually. It's super handy and nice when browsing the Web while going through a lot of pages in a short amount of time. When using proper Web apps it's a total pain + sometimes the history API is not supported correctly so you lose the context entirely (which means you have to start from scratch in whatever app you are using). Gestures in general should be something standard, cross platform / cross browser with a nice API exposed to JavaScript. However, I understand why it's not, they were a mess on Linux until very recently, it's all over the place on Windows, support depends on the hardware, they are not very intuitive, etc.

dewey 6y ago

There are nicer ways to say that, it might just be a tiny bug on a brand new project that someone is sharing.

bluestreak 6y ago

someone already brought this up, there is rationale for it at bottom of this thread

shreddit 6y ago
well, ‘breaking’ basic browser functionality because it breaks the design of your page is not really something i would call rational... As stated some comments below, the code literally says ‘disable back button’
- bluestreak 6y ago
  We will find a way to fix this and have grid scroll without problems at the same time. This is not a dedicated website. This is exactly the same web console that is packages with our free product. It wasn't meant to run on the internet and confuse people. Sorry

santafen 6y ago

As someone else pointed out, and a QuestDB engineer responded, it’s been noted and an issue has been created for it. 5e reasoning for it was actually solid.

MarcellusDrum 6y ago

Yeah an extremely pathetic move.

sirffuzzylogik 6y ago
Sorry for the frustration guys, this was not meant to be "something to lock people in". The rationale for doing this was to prevent macOS users from going back when scrolling the grid horizontally. I submitted a PR to remove this for now, in the future, we will implement a better solution that does not mess with the History API.
- thoraway1010 6y ago
  I'd keep it, I hate working on boxes and when I move left outside box I go back. THAT is the annoyance especially if I'm doing entry work. I'd always wondered WHY this happened.
  - sirffuzzylogik 6y ago
    I have mixed feelings about this feature actually. It's super handy and nice when browsing the Web while going through a lot of pages in a short amount of time. When using proper Web apps it's a total pain + sometimes the history API is not supported correctly so you lose the context entirely (which means you have to start from scratch in whatever app you are using). Gestures in general should be something standard, cross platform / cross browser with a nice API exposed to JavaScript. However, I understand why it's not, they were a mess on Linux until very recently, it's all over the place on Windows, support depends on the hardware, they are not very intuitive, etc.