Vue-grid-layout: Breaks Chrome

[madbolter]

Software version (please complete the following information):

• Browser: Chrome 85.0.4183.121; Firefox 80.0.1
• Vue Version: 2.6.12
• vue-grid-layout version: 2.3.9

Describe the bug
When using dynamic data for layout and items, dragging a widget causes Chrome to freeze. The tab that is displaying the grid is entirely frozen, and any tab that called that tab (like a navbar to load the dashboard tab) is also frozen. F5 has no effect on any affected tab, and Chrome becomes almost unresponsive across all tabs. Closing the offending dashboard (grid view) tab does not restore functionality to the calling tab. Instead, all tabs that were ever related to the grid view must be closed to free up Chrome. Absolutely no problems in Firefox! No JS errors on either console (Chrome or Firefox), and no indication of what is causing Chrome to so totally puke as soon as the drag operation starts.

Please use the CodeSandbox Template to demonstrate your bug. It is much easier for us to help you if you do.

Sorry, it's a commercial application, and the container code (and the widgets) is/are proprietary.

To Reproduce
Steps to reproduce the behavior:

1. Run a dynamic dataset grid of at least two widgets on Chrome and Firefox.
2. Drag one of the widgets in both browsers.
3. Observe everything work perfectly on Firefox and entirely freeze Chrome.

Expected behavior
Vue-grid-layout should work in Chrome as it does in Firefox.

Screenshots
The description should be adequate.

Additional context
The fact that there are no errors and that Firefox runs the same code perfectly tells me that something about how the two browsers are handling the vue-grid-layout drag event is different. Something about this event is problematical, and I don't have time to dig through the vue-grid-layout code to see what could be causing this.

[gmsa]

Just tested with Chrome 85.0.4183.121 on Windows 10, works fine

[madbolter]

And that sort of superficial response is why that problem will remain until
enough people notice it in various contexts and complain enough to compel
you to take it seriously. There is a simple fact of the matter: We have
observed the exact same code to work flawlessly in Firefox and entirely
break Chrome. We are not mistaken about this. So, there is something about
your code that in some situations works fine in Firefox but not in Chrome.

Not my problem to track down for you, so eventually you'll have to deal
with it rather than just ignore it. Good luck.

On Thu, Oct 8, 2020 at 1:34 AM Gustavo Santos [e-mail]
wrote:

Closed #480 https://github.com/jbaysolutions/vue-grid-layout/issues/480.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jbaysolutions/vue-grid-layout/issues/480#event-3853960778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUMQ6PBRDI57C6JF34XJ3SJVTQDANCNFSM4SIDVNDQ
.

--
Richard Jensen, Ph.D.
President, Conclusive Systems LLC
www.conclusivesystems.com
[email protected]
866-234-8164 (office)
303-525-7101 (mobile)

[syshex]

@madbolter Why don't you fix it then and contribute it back to this opensource project?

[madbolter]

Well, see, I did "contribute to this opensource project." Most users
running into such a deal-breaking issue would just abandon the effort and
say nothing. I took the time to write up a bug report, which was summarily
dismissed. I then took the time to respond to the summary dismissal. Ah,
but then the trolls start to emerge.

I was looking for a properly-functioning library. I didn't find it in
vue-grid-layout. I did find it elsewhere. If we wanted to take the time to
track down such a subtle bug and fix it, we would have already written
our own package. We were looking to save time, not fall into a time-sink.
If you do commercial development of enterprise projects, you'll understand.
Otherwise, nothing I say can be of help to you.

In the end, we're happy with the other grid layout library we're now using.
It's not our job to "contribute" to every broken package we try. I did
plenty enough to inform the dev, which, as I say, was summarily dismissed,
making me not a whit interested in "contributing" any further to this
project.

'Nuff said. I won't be responding to more trolling or dog-piling that
emerges.

On Thu, Oct 8, 2020 at 3:38 AM Rui Pereira [e-mail] wrote:

@madbolter https://github.com/madbolter Why don't you fix it then and
contribute it back to this opensource project?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbaysolutions/vue-grid-layout/issues/480#issuecomment-705454205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUMQ67HKNTDOF4BLXWJN3SJWCAJANCNFSM4SIDVNDQ
.

--
Richard Jensen, Ph.D.
President, Conclusive Systems LLC
www.conclusivesystems.com
[email protected]
866-234-8164 (office)
303-525-7101 (mobile)

[gmsa]

Well, we do commercial development, last time I checked open source doesn't pay the bills. Still we managed to make and share this library as open source.
Do you wish a refund for the extraordinary effort you took filling a bug report for a library you can use for free?

[madbolter]

You know, this sort of absurdity is why I typically don't bother to deal
with the open-source "community." The defensiveness and snarky responses
just instantly become epic.

I sent you a bug report. I didn't ask for thanks or any special
consideration. You almost instantly denied there was any issue and closed
the bug report. Fine, at this point I, frankly, don't care what happens
with your project. I "contributed" in my very minimal way, as much effort
as I was prepared to contribute. You instantly rejected it. I "owe" you
nothing more, and I'm not asking for anything at all.

Next time I contemplate submitting a bug report to any open-source project,
I won't bother. I've done it a grand total of twice, and both times I've
regretted it.

Carry on!

On Thu, Oct 8, 2020 at 2:30 PM Gustavo Santos [e-mail]
wrote:

Well, we do commercial development, last time I checked open source
doesn't pay the bills. Still we managed to make and share this library as
open source.
Do you wish a refund for the extraordinary effort you took filling a bug
report for a library you can use for free?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbaysolutions/vue-grid-layout/issues/480#issuecomment-705806125,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUMQ6PH54F33EPZUIJX7LSJYONBANCNFSM4SIDVNDQ
.

--
Richard Jensen, Ph.D.
President, Conclusive Systems LLC
www.conclusivesystems.com
[email protected]
866-234-8164 (office)
303-525-7101 (mobile)

[gmsa]

2 for 2, a smart guy might see a pattern there! 😄
Might be better for you to pay for enterprise licenses!

Good Riddance!

[madbolter]

Oh, that was a good one! Such sweet snark! You are the clear winner here!

On Thu, Oct 8, 2020 at 2:42 PM Gustavo Santos [e-mail]
wrote:

2 for 2, a smart guy might see a pattern there! 😄
Might be better for you to pay for enterprise licenses!

Good Riddance!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbaysolutions/vue-grid-layout/issues/480#issuecomment-705812287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUMQ5RHDMDZ5V6YMNZKMLSJYP4PANCNFSM4SIDVNDQ
.

--
Richard Jensen, Ph.D.
President, Conclusive Systems LLC
www.conclusivesystems.com
[email protected]
866-234-8164 (office)
303-525-7101 (mobile)

[syshex]

@madbolter Don't know what was so wrong about me asking if you would like to do a bit more leg work, submit a fix and contribute... it is not like I was asking for you to re-write the lib.

What I didn't like was the "Not my problem to track down for you" comment. On my chrome (with the reported chrome version) running on linux it is not reproducible, hence, closed. So, it is clearly your problem to track down if you want to use the lib. But anyways, you have found a solution and that is good. Best of luck.

And this is the last you will hear from me here. And I don't say "I wont respond anymore" and then keep on spamming the thread..... went away from the laptop for 2 hours to get some food and get back to this.... you clearly have some free time, could have tracked down the problem in the time you spent here, and helped others with the same problem as you.

[madbolter]

If you can't tell the difference between what you actually said and a nice
query like, "We'd like to take this seriously, but we can't replicate it,
so we'd really appreciate you taking some time to try to track down the
problem, given that you can replicate it in your environment. Thank you in
advance," well, nothing can be said.

Nobody asked for more "legwork" before just summarily closing the issue.
And the clear implication of every comment thus-far has been: "If you're
not willing to personally track down and fix the problem, then you are not
a 'real contributor,' and you shouldn't have the temerity to even submit a
bug report."

Even your idea that if I respond to comments, I must clearly have time to
track down this bug, is obviously false. I will try to respond to even
semi-reasonable comments, although, even that effort has an expiration
date. The "legwork" you suggest I'm responsible to do would be significant.
Whatever is going on with this bug is undoubtedly pretty subtle. I wish the
dev team all success, but rejecting a bug report out of hand does not
contribute to that success. That was my only point, and I still stand by
it. There is a problem, it's certainly subtle, but it is real. Instead of
even attempting to engage with us, nicely asking for follow-up information
(which we then might have been motivated to try to provide), the dev(s)
just dumped the matter, almost instantly. That whole approach, and the
comments that followed, entirely demotivates us to further "contribute" to
this project.

We do wish you all success with the project, but the approach taken
regarding this bug report demovitates rather that motivates eliciting help.

On Thu, Oct 8, 2020 at 3:45 PM Rui Pereira [e-mail] wrote:

@madbolter https://github.com/madbolter Don't know what was so wrong
about me asking if you would like to do a bit more leg work, submit a fix
and contribute... it is not like I was asking for you to re-write the lib.

What I didn't like was the "Not my problem to track down for you" comment.
On my chrome (with the reported chrome version) running on linux it is not
reproducible, hence, closed. So, it is clearly your problem to track down
if you want to use the lib. But anyways, you have found a solution and that
is good. Best of luck.

And this is the last you will hear from me here. And I don't say "I wont
respond anymore" and then keep on spamming the thread..... went away from
the laptop for 2 hours to get some food and get back to this.... you
clearly have some free time, could have tracked down the problem in the
time you spent here, and helped others with the same problem as you.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbaysolutions/vue-grid-layout/issues/480#issuecomment-705840287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUMQ56X6KJOE4LR7XCD43SJYXGXANCNFSM4SIDVNDQ
.

--
Richard Jensen, Ph.D.
President, Conclusive Systems LLC
www.conclusivesystems.com
[email protected]
866-234-8164 (office)
303-525-7101 (mobile)