Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE (www.oxfordhandbooks.com). © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy and Legal Notice).

date: 07 August 2020

Abstract and Keywords

This chapter is concerned with sexual conflicts in romantic jealousy. An outline of the indispensable ingredients and boundaries of romantic jealousy is followed by a description of the functioning of the psychological mechanisms underlying romantic jealousy. This description is guided by (a) evolutionary psychological assumptions about emotions in general, and (b) two conceptually important distinctions concerning romantic jealousy. The first distinction refers to whether the partner’s infidelity is merely suspected or has actually occurred. Following Parrott (1991), the two variants of the jealousy mechanism are referred to as suspicious and fait accompli jealousy. The second distinction refers to the nature of the infidelity and its implications for men’s and women’s reproductive success. An evolutionary view of romantic jealousy suggests that a partner’s sexual infidelity is more threatening to male than female reproductive success, whereas emotional infidelity poses a greater threat to female than male reproductive success. Some suggestions for future research on romantic jealousy conclude this chapter.

Keywords: romantic jealousy, evolutionary psychology, sexual conflict, suspicious jealousy, fait accompli jealousy

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.