fix(popup)!: `moved="any"`, `enter` default, `callback=fn` #622

errael · 2024-09-19T19:38:55Z

(I'm looking at adding mousemoved='any', close='click', and popup_close() to popups; came across a few things to fix first.)

To reviewers
This is my first neovim related PR and my first lua code. Suggestions about style... welcome. Not sure how this repo handles reviews, so I'm tagging some names that have done some popup work (sorry for the noise). There's some TODO I scattered with questions, looking for feedback (would like to remove before merge). There's a probable bug in tbl.apply_defaults, noted in popup/utils.lua.

@l-kershaw @fdschmidt93 @AlejandroSuero @xactlyblue @jesseleite
@Conni2461 @tjdevries

Fix moved = 'any' option.
Before this PR, the popup option "moved = 'any'," gets an exception because of changes made to vim.lsp.util.close_preview_autocmd:
- refactor(lua): use api to replace vim.cmd neovim/neovim#19283 changed the behavior,
- fix(ui): close floating window on BufLeave event neovim/neovim#16557 changed the accessibility,
Those changes looks like a fix. The now private code from "...lsp.util" is copied in here and the the buffer numbers are added as needed for the new code.
Default the new option enter to false
Changed the default to false, so the behavior matches vim with no options; which is to leave the cursor where it was and not change the focus to the popup. Is there a place to note breaking changes? Wonder the reason for "enter" option?
Fix callback
I couldn't get it to work in a simple case. Converted to an autocmd. Comments on potential timing issues? Accessing buffer in callback does work. There's some preliminary work to support "popup_close(win_id, result)" and mouse stuff for a later PR.
Update POPUP.md

Tests

The options callback and enter are tested. The option moved only has a partial test which verifies the option can be used (it fails without this PR). #622 (comment) details the problems I'm having with getting the tests to work. Will revisit if/when I understand the trick that's needed.

Could also do ...

There's dict_default(). Would using tbl.apply_defaults make sense? Seems cleaner.
Should tbl.apply_defaults do a deepcopy of any table from defaults?

There was a comment around the callback setup.

Giving win_id is pointless here because it's closed right afterwards
but it might make more sense once hidden is implemented

I've removed the comment. The called back function may want to know the win_id; for example,
there could be a data structure associated with the win_id that can be freed.

PS: For the stuff I'm looking at adding, I could open a discussion or just do the PR and discuss there; recommendation?

AlejandroSuero · 2024-09-19T20:05:45Z

@errael I am not too familiar with the codebase itself but I can solve some of the questions

To run test:

make test see Makefile if you want to know what it does.
Reference to plenary.test_harness.

To make test:

Reference to lua testing with busted style(it's the style that plenary uses).
Check the tests/plenary/popup_spec.lua to see some examples (it's what I did).

To check code style:

Check the files you touched and make a similar style.
Check the linter passes when using make lint (same Makefile as before).

The next thing I am not so sure about, but I think this PR will "break" things in comparison with the master branch so it would be nice to use the conventional commits syntax to display it, i.e. fix(popup)!: .... Also commenting it in the PR itself often helps to see it before checking the code (at least for me).

errael · 2024-09-19T21:51:57Z

@AlejandroSuero Thanks so much; very useful. luacheck was yet another thing to install. The commit syntax you mean is the ! in the message; cool.

I was going to ask about running just popup tests. But got around to doing the following on the command line

nvim --headless --noplugin -u scripts/minimal.vim -c "PlenaryBustedDirectory 
    tests/plenary/popup_spec.lua {minimal_init = 'tests/minimal_init.vim', sequential = true}"

which seemed to work.

It's been so many years since I've messed with makefiles... Wanting to use the Makefile to run only popup_spec.lua, this seems to work

... "PlenaryBustedDirectory tests/plenary/$(TEST1) {mi...

and doing

TEST1=popup_spec.lua make test

Is there something else that makes sense? I'll include this change in the PR, can always take it out.

One test, out of all the tests, is failing. Is this something to file an issue about?

AlejandroSuero · 2024-09-19T22:27:16Z

@errael to test single files you can change or create a target on the Makefile, the PlenaryBustedDirectory with PlenaryTestFile as indicated in the reference plenary.test_harness that I linked before.

I will stick to the testing the whole suite in case some other modules make use of popup. Also is what is used on CI. But this something that @Conni2461 and @tjdevries should know better to explain why there is no target for test-file passing the file as arguments.

Regarding the test failure, right now Im on my mobile so its a pain to check it tbh, but no ones resolves your question, tomorrow when I wake I see what could be the point of failure 😊

errael · 2024-09-20T01:46:36Z

I've added some tests. I've run into a problem. In particular async(), from busted, is not found.

Here's the use case

move the cursor with vim.fn.cursor(2, 1)
let the cursor move events and autocommands propagate
check that things happened as expected

The code can be seen in popup_spec.lua around line 195 in the PR after

    it("with moved", function()
      async()

/src/tools/neovim/plenary.nvim/tests/plenary/popup_spec.lua:196: attempt to call global 'async' (a nil value)

errael · 2024-09-20T02:05:37Z

Regarding the test failure, right now Im on my mobile so its a pain to check it tbh, but no ones resolves your question, tomorrow when I wake I see what could be the point of failure 😊

What I'm seeing

Testing: 	/junk/repo/neovim/plenary.nvim/tests/plenary/scandir_spec.lua	
Success	||	scandir can list all files recursive with cwd	
...
Success	||	scandir ls works for cwd	
Success	||	scandir ls works for another directory	
Fail	||	scandir ls works with opts.hidden for cwd	
            .../repo/neovim/plenary.nvim/tests/plenary/scandir_spec.lua:246: Expected objects to be the same.
            Passed in:
            (boolean) false
            Expected:
            (boolean) true
            
            stack traceback:
            	.../repo/neovim/plenary.nvim/tests/plenary/scandir_spec.lua:246: in function <.../repo/neovim/plenary.nvim/tests/plenary/scandir_spec.lua:240>
            	
	
Success: 	21	
Failed : 	1	
Errors : 	0

errael · 2024-09-20T05:56:49Z

Make it ready for review.

Test callback option OK. Test enter option OK.

Test moved option has problems; it's commented out. Pretty sure the test is flawed. I'll address it with the next PR.

AlejandroSuero · 2024-09-20T06:02:46Z

@errael The principal issue I see is that async() is not defined (it doesn't exists), so does timer and done.

In my case, scandir_spec.lua doesn't fail.

Here is the error that async throws in my end.

Fail || plenary.popup moved option without moved
     .../aome/personal/plenary.nvim/tests/plenary/popup_spec.lua:179: attempt to call global 'async' (a nil value)
            
     stack traceback:
       .../path/to/plenary.nvim/tests/plenary/popup_spec.lua:179: in function <.../path/to/plenary.nvim/tests/plenary/popup_spec.lua:178>
            
Fail || plenary.popup moved option with moved
     .../path/to/plenary.nvim/tests/plenary/popup_spec.lua:195: attempt to call global 'async' (a nil value)
            
      stack traceback:
        .../path/to/plenary.nvim/tests/plenary/popup_spec.lua:195: in function <.../path/to/plenary.nvim/tests/plenary/popup_spec.lua:194>

AlejandroSuero · 2024-09-20T06:13:06Z

You can use either vim.defer_fn or vim.schedule_wrap or require "plenary.job" and make use of Job:new.

Some examples in async_testing_spec.

Also in tests/plenary/async/async_spec.lua you can see how to use "plenary.async".tests.add_to_env() to make the it async.

AlejandroSuero · 2024-09-20T06:24:00Z

@errael I made the following changes, in case you want me to commit it to your branch.

-- at the top
require("plenary.async").tests.add_to_env() -- this lets you use the `a` variable to make it async
-- ...
  a.describe("moved option", function()
    local function populate()
      local wnr = vim.fn.winnr()
      local bnr = vim.fn.winbufnr(wnr)
      vim.fn.setbufline(bnr, 1, {"one", "two", "three", "four"})
      vim.fn.cursor(1, 1)
    end
    local callback_result
    local function callback(wid, result)
      callback_result = result
    end

    a.it("without moved", function()
      -- removed aync()
      callback_result = nil
      populate()
      local win_id = popup.create("hello there", {
        callback = callback,
      })
      -- move the cursor, should not do callback
      vim.fn.cursor(2, 1)
      local timer = vim.uv.new_timer() -- declared timer
      timer:start(10, 0, function()
        eq(nil, callback_result)
        vim.api.nvim_win_close(win_id, true)
      end)
      -- removed done()
    end)

    a.it("with moved", function()
      -- removed async()
      callback_result = nil
      populate()
      local win_id = popup.create("hello there", {
        moved = "any",
        callback = callback,
      })
      -- move the cursor, window closes and callback invoked
      vim.fn.cursor(2, 1)
      local timer = vim.uv.new_timer() -- declared timer
      timer:start(10, 0, function()
        eq(-1, callback_result)
        if -1 ~= callback_result then
          -- window wasn't closed
          vim.api.nvim_win_close(win_id, true)
        end
        -- removed done()
      end)
    end)
  end)

errael · 2024-09-20T15:16:02Z

You can use either vim.defer_fn or vim.schedule_wrap or require "plenary.job" and make use of Job:new.

Cool. vim.defer_fn looks convenient. I'll play around with those.

Some examples in async_testing_spec.

Also in tests/plenary/async/async_spec.lua you can see how to use "plenary.async".tests.add_to_env() to make the it async.

Thanks for the notes on using async. I'll take a look at the references you provided; appreciated. So the busted async isn't available I guess. I'll have to think about why the done wouldn't be needed.

No need to do the commit, thanks for taking a look. So much new stuff ...

errael · 2024-09-20T23:54:22Z

I'll update the OP, with status of the tests. But here's a detailed look at the moved = "any" tests that are commented out. There is one of the tests that runs; the test does nothing. But it does fail without this PR because of changes made a few years ago.

Source the following lua file. With the nvim_win_close the callback is invoked before exit. Without it, the callback is invoked immediately after exit. Before sourcing the cursor should not be on the 2nd character. If the cursor is on the 2nd character then no callback and the popup is visible when the script completes; at this point move the cursor and the popup exits.

The cursor move autocmd that triggers the callback does not happen until the script exits. I'm guessing its because the cursor isn't actually moved until it's in the top level main loop (if that's a viable concept) and the screen is drawn. Given this comment in vim.wait

Nvim still processes other events during this time.

I had hopes; but who knows what the "other events" encompasses. I tried various vim.def_fn and vim.wait things.

local Popup = require 'plenary.popup'

local msgs = {}
local function add_msg(msg)
    table.insert(msgs, os.date('!%T') .. ': ' .. msg)
end

local callback_result
local function callback(wid, result)
    add_msg('CALLBACK' .. tostring(result))
    vim.print(os.date('!%T') .. ': CALLBACK ' .. tostring(result))
    callback_result = result
end

add_msg('Start')

callback_result = nil
vim.fn.cursor(1, 1)

local main_wid = vim.fn.win_getid()
local popup_wid = Popup.create("hello there", {
    moved = "any",
    callback = callback,
})
vim.fn.feedkeys(' ', 'x')

add_msg('Exit ' .. tostring(callback_result))
vim.print(vim.inspect(msgs))

Output showing callback after exit

{ "22:55:15: Start", "22:55:15: Exit nil" }
22:55:15: CALLBACK -1

errael · 2024-09-21T00:02:02Z

@Conni2461 @AlejandroSuero (and any cognizant lurkers) I think this is ready. There's questions, but it seems to work as advertised.

errael · 2024-09-21T05:37:56Z

In my case, scandir_spec.lua doesn't fail.

@AlejandroSuero The "failure" I'm seeing on my system is expected because I'm using hg-git, not git, so

eq(true, contains_match(dirs, "%.git$"))

fails.

AlejandroSuero · 2024-09-21T12:58:16Z

@errael I suspect that this is the expected behaviour right?

And when moving the cursor, then it prints something like:

{ "22:55:15: Start", "22:55:15: Exit nil" }
22:55:15: CALLBACK -1

AlejandroSuero · 2024-09-21T13:01:47Z

tests/plenary/popup_spec.lua

@@ -160,3 +303,4 @@ describe("plenary.popup", function()
    end)
  end)
 end)
+-- vim:sw=2 ts=2 et


This should be removed cause it can mess up other peoples environments, better to keep it in your config.

Somewhere like path/to/your/config/after/ftplugin/lua.lua if you only want to set it for lua files.

I leave you an example of using this in my config for Golang

So the use of a modeline is not the style in plenary.nvim. It's nice to have stuff local instead of global. Oh well. I'll take it out

While I'm figuring out lua... I'll use

autocmd BufRead */plenary.nvim/*.lua set sw=2 ts=2 sts=2 noet

This should be removed cause it can mess up other peoples environments, better to keep it in your config.

BTW, there's set nomodeline or set modelines=0 to avoid modelines modifying your environment.

I just came across :help editorconfig

Think of it like 'modeline' for an entire (recursive) directory.

Adding such a file to the plenary.nvim repo might be useful.

AlejandroSuero · 2024-09-21T13:08:34Z

Also I applied the formatter on the file and got this diff

The project uses StyLua for the formatting rules and this is how its applied later on CI.

plenary.nvim/.github/workflows/default.yml

Lines 45 to 55 in 2d9b061

    
             stylua: 
        
               name: stylua 
        
               runs-on: ubuntu-22.04 
        
               steps: 
        
                 - uses: actions/checkout@v3 
        
                 - uses: JohnnyMorganz/stylua-action@v2 
        
                   with: 
        
                     token: ${{ secrets.GITHUB_TOKEN }} 
        
                     version: latest 
        
                     # CLI arguments 
        
                     args: --color always --check .

You can either use the cli like stylua -f ./.stylua.toml --check . to check for formatting errors or stylua -f ./.stylua.toml . to fix them. Another way is using a plugin to attach formatters, I personally use none-ls the successor of null-ls RIP, but there are others out there.

errael · 2024-09-21T14:43:52Z

I suspect that this is the expected behaviour right?
...
And when moving the cursor, then it prints something like:
{ "22:55:15: Start", "22:55:15: Exit nil" }
22:55:15: CALLBACK -1

I guess this is the expected behavior, no cursor move events until the screen is drawn with the cursor in a different location; but it makes it difficult to write tests. There is undoubtedly a way to do it, I don't know what it is; and it may not be worth the effort.

To contrast, notice with nvim_win_close before the script exits

 vim.fn.feedkeys(' ', 'x')
 
+vim.api.nvim_win_close(popup_wid, true)
+
 add_msg('Exit ' .. tostring(callback_result))
 vim.print(vim.inspect(msgs))

that the callback is invoked before exit, and so that can be checked. Note the Exit -1 instead of Exit nil.

14:03:30: CALLBACK -1                                                                     
{ "14:03:30: Start", "14:03:30: CALLBACK-1", "14:03:30: Exit -1" }

errael · 2024-09-21T15:14:55Z

Also I applied the formatter on the file and got this diff

Thanks, I'll checkout installing StyLua locally.

errael · 2024-09-21T15:32:46Z

Updated after a review.

I guess there may be no one still working with plenary.vim familiar with and interested in popup compatibility for a technical review.

errael · 2024-09-21T16:01:53Z

Update for StyLua of the runtime code in this PR.

errael · 2024-09-27T16:52:37Z

Oops, forgot to remove the modeline. Done.

@Conni2461 @tjdevries This PR fixes issues in existing popup code; see OP.

I have a 2nd PR ready to open with some additional popup commands.
There's some neovim enhancements under discussion which allows a 3rd PR that implements some of the missing mouse capabilities.
- getmousepos() doesn't find non-focusable windows neovim/neovim#30490
- mouse event for buffer in non-focusable window neovim/neovim#30504

Looking for some advisement on getting reviews and merge or reject.

AlejandroSuero · 2024-10-09T10:24:45Z

Makefile

+test1:
+	nvim --headless --noplugin -u scripts/minimal.vim -c "PlenaryBustedDirectory tests/plenary/$(TEST1) {minimal_init = 'tests/minimal_init.vim', sequential = true}"
+


If you want to add this to the Makefile targets I think it should be it's separated PR. But if @tjdevries or @Conni2461 thinks it's okay to leave it in this one, then it won't be needed.

Removed the change. I'll maintain it locally.

AlejandroSuero · 2024-10-09T10:29:42Z

tests/plenary/popup_spec.lua

+    local function populate()
+      local wnr = vim.fn.winnr()
+      local bnr = vim.fn.winbufnr(wnr)
+      vim.fn.setbufline(bnr, 1, { "--one--", "--two--", "--three--", "--four--" })
+      vim.fn.cursor(1, 1)
+    end
+    ]]
+
+    --[[
+    it("without moved", function()
+      --async()
+      callback_result = nil
+      populate()
+      local popup_wid = popup.create("hello there", {
+        callback = callback,
+      })
+      -- move the cursor, should not do callback
+      vim.fn.cursor(2, 1)
+      local timer = vim.uv.new_timer()
+      timer:start(10, 0, function()
+        eq(nil, callback_result)
+        vim.api.nvim_win_close(popup_wid, true)
+        --done()
+      end)
+    end)
+    ]]
+
+    --[[
+    it("with moved", function()
+      --async()
+      callback_result = nil
+      populate()
+      local popup_wid = popup.create("hello there", {
+        moved = "any",
+        callback = callback,
+      })
+      -- move the cursor, window closes and callback invoked
+      vim.fn.cursor(2, 1)
+      local done = false
+      vim.defer_fn(function()
+        --eq(-1, callback_result)
+        --eq(0, callback_result)
+        done = true
+      end, 100)
+      vim.wait(100, function()
+        eq(0, callback_result)
+        return done
+      end, 60)
+      --if -1 ~= callback_result then
+      --  -- window wasn't closed
+      --  vim.api.nvim_win_close(popup_wid, true)
+      --end
+
+      --local timer = vim.uv.new_timer()
+      --timer:start(10, 0, function()
+      --  eq(-1, callback_result)
+      --  if -1 ~= callback_result then
+      --    -- window wasn't closed
+      --    vim.api.nvim_win_close(popup_wid, true)
+      --  end
+      --  --done()
+      --end)
+    end)
+    ]]


If this won't be used in the end, remove it along with the require("plenary.async").tests.add_to_env() comment on line 2, but if you want to try and add the async testing functionality, you can head to async test folder and see how it's used there.

I took this out and stashed it. I'll reconsider adding it at a later time.

AlejandroSuero · 2024-10-09T10:33:21Z

lua/plenary/popup/init.lua

  end

+  -- TODO: Wonder what this is about? Debug? Convenience to get bufnr?


I think what this does if I'm not mistaken @tjdevries @Conni2461 it's that checks for vim_options.finalize_callback to be (it could be null) and if does exists calls it, maybe there's a part of the code where it removes it or it's set to false, will look into that.

vim_options.finalize_callback

The question is about why it exists at all. It was added with #513.

@xactlyblue Could you clarify the purpose of #513? It doesn't seem to have anything to do with popups.

Yeah why it exists, that idk, if @xactlyblue could clarify on that regard, would be nice. I tried to find where it was being used or defined and this is what I got.

I added this to log when it's called or not:

Results from make test:

Video demo when using Telescope which creates a popup:

finalize_callback-demo.mp4

Note

As you can see it adds the not called log twice because I think Telescope calls it twice for each one it creates. I used Telescope 3 times, and got 6 not called logs.

Tried both in this PR and in master btw, in case it was related to something this PR was removing.

if @xactlyblue could clarify on that regard

Hey.

I made that change a while ago to address a problem I was having where I needed to access some information about the buffer created for the popup (I forgot the details to be honest, but if you need them I could probably go through my dotfiles commit history to figure out what my specific use-case was at the time).

It just creates an easier way for the user to manually access the bufnr and win_id of the popup for whatever reason they might need it. There isn't any internal implementation or usage of it.

I probably should've added a comment explaining the changes to clear the purpose up, sorry for any confusion!

creates an easier way for the user to manually access the bufnr and win_id

Thanks, no problem. Debug convenience. Do you agree there's no reason to keep it in a final product?

Consider nvim_win_get_buf(win_id)

Sorry, I should have clarified: this change was meant to be accessible by the user (for whatever reason they may need to access the bufnr and win_id of a created popup).

I'm not really familiar with the inner-workings of plenary or it's API, so I apologize if this change was unnecessary, but I couldn't find any existing method to easily access the bufnr of a created popup via a callback, so I figured the simplest solution would be to add an optional callback to allow the user to access the bufnr and win_id as soon as they're available.

If I recall correctly my use-case had something to do with zindex/overlap issues in a plugin that allowed you to supply popup arguments to plenary, which is why I made it a callback (I guess I figured it was more useful/elegant to add a general callback for plenary instead of modifying the plugin itself) the user can supply.

I looked through my NeoVim configuration and I'm not currently using it so I personally don't mind if it's removed but I'm not sure if anyone else is making use of it in their own configurations (though I'd guess the odds of that are fairly slim considering it's not really documented anywhere and has fairly specific use-cases).

I understood (I think). I didn't see a reason for it, other than convenience.

simple, existing method to access the bufnr of a created popup

I'm new to neovim, I don't know what was available when. Currently nvim_win_get_buf(win_id) or winbufnr() gets the buffer number from a window. May be other ways.

I'm not asking you to remove it, just wanted to make sure there wasn't something I missed.

fix(popup): moved="any", enter default, callback=fn

cc176c9

errael marked this pull request as draft September 19, 2024 19:39

errael changed the title ~~fix(popup): moved="any", enter default, callback=fn~~ fix(popup)!: moved="any", enter default, callback=fn Sep 19, 2024

errael force-pushed the PopupFix branch from 18ac880 to b3e44d5 Compare September 20, 2024 01:33

errael marked this pull request as ready for review September 20, 2024 05:56

errael force-pushed the PopupFix branch from b3e44d5 to a0ae655 Compare September 20, 2024 05:58

errael force-pushed the PopupFix branch from a0ae655 to c83dce7 Compare September 20, 2024 15:00

errael force-pushed the PopupFix branch from c83dce7 to 2299083 Compare September 20, 2024 20:41

AlejandroSuero reviewed Sep 21, 2024

View reviewed changes

errael force-pushed the PopupFix branch 2 times, most recently from 12574a1 to 4f0bbe2 Compare September 21, 2024 15:17

errael force-pushed the PopupFix branch from 4f0bbe2 to c82b8af Compare September 21, 2024 15:56

errael force-pushed the PopupFix branch 2 times, most recently from 3e64044 to 41c4d03 Compare September 27, 2024 16:02

errael requested a review from AlejandroSuero September 27, 2024 16:14

AlejandroSuero suggested changes Oct 9, 2024

View reviewed changes

AlejandroSuero reviewed Oct 9, 2024

View reviewed changes

errael force-pushed the PopupFix branch 2 times, most recently from a2b6c91 to cc176c9 Compare October 9, 2024 15:56

errael requested a review from AlejandroSuero October 9, 2024 15:58

AlejandroSuero approved these changes Oct 9, 2024

View reviewed changes

		test1:
		nvim --headless --noplugin -u scripts/minimal.vim -c "PlenaryBustedDirectory tests/plenary/$(TEST1) {minimal_init = 'tests/minimal_init.vim', sequential = true}"

		end

		-- TODO: Wonder what this is about? Debug? Convenience to get bufnr?

fix(popup)!: moved="any", enter default, callback=fn #622

Are you sure you want to change the base?

fix(popup)!: moved="any", enter default, callback=fn #622

Conversation

errael commented Sep 19, 2024 • edited Loading

AlejandroSuero commented Sep 19, 2024

errael commented Sep 19, 2024

AlejandroSuero commented Sep 19, 2024

errael commented Sep 20, 2024

errael commented Sep 20, 2024

errael commented Sep 20, 2024

AlejandroSuero commented Sep 20, 2024

AlejandroSuero commented Sep 20, 2024

AlejandroSuero commented Sep 20, 2024

errael commented Sep 20, 2024

errael commented Sep 20, 2024 • edited Loading

errael commented Sep 21, 2024

errael commented Sep 21, 2024

AlejandroSuero commented Sep 21, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AlejandroSuero commented Sep 21, 2024

errael commented Sep 21, 2024

errael commented Sep 21, 2024

errael commented Sep 21, 2024

errael commented Sep 21, 2024

errael commented Sep 27, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AlejandroSuero Oct 9, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xactlyblue Oct 11, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xactlyblue Oct 11, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fix(popup)!: `moved="any"`, `enter` default, `callback=fn` #622

fix(popup)!: `moved="any"`, `enter` default, `callback=fn` #622

errael commented Sep 19, 2024 •

edited

Loading

errael commented Sep 20, 2024 •

edited

Loading

AlejandroSuero Oct 9, 2024 •

edited

Loading

xactlyblue Oct 11, 2024 •

edited

Loading

xactlyblue Oct 11, 2024 •

edited

Loading