Skip to main content

jQuery updating ancestor content when nested element is removed

I am using jQuery 3.6

I am deleting a nested element from a portion of my page, and I want that section of the page to automatically update, to reflect the change - I was expecting the browser to automatically update the modified section, but it doesn't and the change is only visible when I refresh the page.

Here is a snippet of the HTML:

 <div id="foo" class="row text-center text-lg-left">

    <div class="col-lg-3 col-md-4 col-6">
      <a id="abc-1"><img src="image1"></a>
    </div>

    <div class="col-lg-3 col-md-4 col-6">
      <a id="abc-2"><img src="image2"></a>
    </div>

    <!-- etc -->

</div>

Here is my Javascript snippet:

 $.ajax({
                type: 'post',
                url: "/path/to/post/to",
                data: {'identifier': $(this).attr('id'), 'status':1, 'csrfmiddlewaretoken': '1234567abc'},,
                success: function(data) {
                   /* assume we have variable named 'identifier' ... */
                   $(`a#${identifier}`).parent().remove();
                   
                   /* next two lines is a brute-force attempt to
                      force the element to update - but it still
                      doesn't update, until I refresh the page!
                   */
                   let remaining_content = $('div#foo').html()
                   $('div#foo').html(remaining_content);
                },
                error: function(xhr, status, error) {
                  var err = JSON.parse(xhr.responseText);
                  alert(status);
                  alert(error);
                  alert(err.Message);
                }    
});

How do I get the div with id foo to update (ideally with some nice color fade-in/out) when it's content changes (deletion of elements in this case) - without having to refresh the browser to observe the change?

Via Active questions tagged javascript - Stack Overflow https://ift.tt/2FdjaAW

Comments

Popular posts from this blog

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...