Hi,

In my opinion,

Hi,

when discussing [0], a question arose. When phpMyAdmin thinks that there are no rows, some tabs are greyed out. However they can still be clicked , because by the time the page has been displayed, another process might have written some rows to this table.

I am quite confusing about "another process might have written some rows to this table." We can't assume that another process is doing something. TCP is stateless which means in current moments, the Table is empty. so we should "2. grey out but not clickable" for current page

When user refreshes the page, they can see the data.

But clickable greyed out tabs is confusing for some users. Let's decide about this (for 4.1):

1. no longer grey out

2. grey out but not clickable

3. status quo

[0] https://sourceforge.net/p/phpmyadmin/bugs/3904/

--

xmujay (Bin Zu)

On 05/06/2013 01:01 PM, Marc Delisle wrote:

Hi,

when discussing [0], a question arose. When phpMyAdmin thinks that there are no rows, some tabs are greyed out. However they can still be clicked , because by the time the page has been displayed, another process might have written some rows to this table.

But clickable greyed out tabs is confusing for some users. Let's decide about this (for 4.1):

1. no longer grey out

2. grey out but not clickable

3. status quo

[0] https://sourceforge.net/p/phpmyadmin/bugs/3904/

I'm only against #2, as we shouldn't force a manual refresh of the page.

Bye, Rouslan