{"id":53634,"date":"2016-09-30T11:27:00","date_gmt":"2016-09-30T16:27:00","guid":{"rendered":"https:\/\/content.findlaw-admin.com\/ability-legal\/supreme\/legal-commentary\/the-lessons-of-the-supreme-courts-recent-decision-granting-a-huge-victory-to-exxon-in-the-exxon-valdez-oil-spill-case.html"},"modified":"2016-09-30T11:27:00","modified_gmt":"2016-09-30T16:27:00","slug":"the-lessons-of-the-supreme-courts-recent-decision-granting-a-huge-victory-to-exxon-in-the-exxon-valdez-oil-spill-case","status":"publish","type":"supreme","link":"https:\/\/supreme.findlaw.com\/legal-commentary\/the-lessons-of-the-supreme-courts-recent-decision-granting-a-huge-victory-to-exxon-in-the-exxon-valdez-oil-spill-case.html","title":{"rendered":"The Lessons of the Supreme Court&#8217;s Recent Decision Granting a Huge Victory to Exxon in the Exxon Valdez Oil Spill Case"},"content":{"rendered":"\n<div class=\"wp-container-core-columns-is-layout-9d6595d7  fl-block-columns fl-sectionWithSidebar fl-container fl-flex fl-flex-wrap fl-gap30\">\n    \n    <div class=\"fl-page-articles   fl-block-column fl-section-main fl-section-main-full-width\">\n        <div class=\"yui-g\" id=\"leftcol-module\">\n      <!-- Right Line of Links Section -->\n      <!-- BEGIN PICTURE INSERTION -->\n      <!-- BEGIN TITLE AND AUTHOR INSERTION -->\n      <table>\n        <tr>\n\n          <td width=\"100\" rowspan=\"3\" class=\"wiauthor\"><a href=\"\/legal-commentary\/anthony-sebok-archive\"><img decoding=\"async\" src=\"https://supreme.findlaw.com/static/f/images\/writ\/anthony.sebok.jpg\" border=\"0\"><\/a><\/td>\n          <td class=\"wititle\"><h1>The Lessons of the Supreme Court&#8217;s Recent Decision Granting a Huge Victory to Exxon in the Exxon Valdez Oil Spill Case<\/h1><\/td>\n        <\/tr>\n        <tr>\n          <td class=\"wiauthor\"><a href=\"\/legal-commentary\/anthony-sebok-archive\" class=\"graybold\"><h2>By ANTHONY J. SEBOK <\/h2><br><\/a><\/td>\n        <\/tr>\n        <tr>\n          <td class=\"widate\">Tuesday, Jul. 1, 2008<\/td>\n\n        <\/tr>\n      <\/table>\n\n<span class=\"smalltext\">\n\n\n <p>Last week, in <strong><i><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/554\/471.html\" rel=\"noopener\">Exxon  Shipping Co. v. Grant Baker, et. al.,<\/a><\/i><\/strong> the Supreme Court gave the  defendants, Exxon, a huge victory. It  reduced a $2.5 punitive damages award\u2014the largest ever awarded in a federal  court\u2014to $507 million. <\/p>  \n \n<p>In this column, I will examine the lessons we can draw  from the Court\u2019s decision. The real  import of the decision, I shall argue, may not lie in what the Court said, but  rather in the peculiar voting bloc of Justices that produced the ruling in  favor of Exxon.<\/p><\/span>\n<span class=\"smalltext\">\n  <!-- START TABLE FOR RELATED -->\n   \n<!-- 300x250 AD -->\n\n  <p><strong>The Relevant  Facts, the Jury Verdict, and the Ninth Circuit Decision<\/strong><\/p>\n  <\/span>\n<p>The underlying facts behind the case are well known. In 1989, an Exxon supertanker spilled 11  million gallons of crude oil into the Prince William Sound in Alaska. Exxon spent $2.1 billion in a voluntary  clean-up effort, and then settled or pled guilty to numerous civil and criminal  actions brought against it by the State of Alaska and the federal  government. The suit in question here,  however, arose from a separate suit \u2013 a class action brought by commercial  fishermen, Native Americans, and landowners whose livelihoods and property were  damaged by the spill.<\/p>\n<p>At the trial, the jury heard evidence concerning how the  captain of the tanker, a \u201crecovered\u201d alcoholic, had relapsed, and was piloting  the huge vessel drunk. The jury also  heard evidence that management at Exxon knew about the captain\u2019s relapse, yet  had not stripped him of his duties. In  the end, the district judge held that the evidence indicated that Exxon had  caused approximately $507.5 million in damage (although the jury actually  awarded a lesser sum to the plaintiffs to represent compensatory damages for  the harm caused), and the jury awarded the plaintiffs $5 billion in punitive  damages. This amount was later reduced  to $2.5 billion by the Ninth Circuit.<\/p>\n<p><strong>The Three Grounds for Supreme Court  Review<\/strong><\/p>\n<p>The Supreme Court then granted review. There were three grounds for Exxon\u2019s  challenging the $2.5 billion award of punitive damages. None of them involved the question whether  the award violated the Due Process limitations on punitive damages created by  the Court in earlier decisions. Instead,  all three were based on the award\u2019s permissibility under maritime law, which is  one of the last areas of substantive federal common law left to the federal  courts. (\u201cCommon law\u201d is judge-made; in  contrast, the lion\u2019s share of federal law derives from interpretations of federal  statutes or the U.S. Constitution.) <\/p>\n<p>The first argument Exxon presented was that maritime common  law does not permit the awarding of punitive damages against a principal or an  employer for the recklessness of its agents or employees. The second argument was that maritime common  law had been preempted by various federal statutes in this case &#8212; statutes  that did not authorize punitive damages in the event of civil actions based on  their violation. I will not discuss these first two arguments.\u00a0 The Court split   evenly over the first question, thus leaving the Ninth Circuit&#8217;s interpretation   standing, albeit without establishing a holding.\u00a0 The author of the   Court&#8217;s opinion, Justice Souter, thought that the second argument was pretty   weak, \u00a0the portion of the opinion in which he refutes it was joined   by all eight participating Justices. (Justice Alito did not participate in the   decision).\n<\/p>\n<p><strong>The Argument that Convinced the Court  to Dramatically Reduce the Verdict \u2013 and Why It is Not as Strange as It May  Seem<\/strong><\/p>\n<p>The third argument Exxon presented was that, as a matter of  common law, the $2.5 billion award was excessive. The Court\u2019s participating Justices voted five-to-three  to accept this argument. Before I  review Souter\u2019s opinion for the majority, it is important to acknowledge what  is both strange and not-so-strange about Exxon\u2019s winning argument. <\/p>\n<p>To begin, it might seem strange that the United State Supreme  Court was being asked to answer a question about substantive tort law. Ever since the landmark Supreme Court  precedent <strong><i><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/304\/64.html\" rel=\"noopener\">Erie v.  Pennsylvania<\/a><\/i><\/strong>, law students have been taught that the federal  courts do not make law, but only apply law found in other sources (state common  law, or state and federal statutes and constitutions). This view of <i>Erie<\/i> has always been overly simplistic, if not na\u00efve. There is still lots of federal common law,  and even a federal common law of torts.  Maritime law is one of the purest examples of this point. So the question asked by Exxon was not that  strange.<\/p>\n<p><strong>The Court\u2019s Analysis: Looking to History and Policy, But  Erroneously So<\/strong><\/p>\n<p>How did Souter answer that question? In my view, his answer was a little  disappointing, especially since of all nine Justices on the Court, Souter is  the one judge with decades of experience as a common law judge. He came to the Court from the New Hampshire  Supreme Court, where he had been deciding cases about the common law of torts  and contracts for years.<\/p>\n<p>As Justice Oliver Wendell Holmes and Benjamin Cardozo taught  us, common law adjudication requires, at the crudest level, a balancing of  history (precedent) and policy (normative judgment). Souter attempted to take both these  dimensions into account in the Exxon Valdez case, but his methodology is so  flawed that it brings the Court\u2019s result into question.<\/p>\n<p>Let\u2019s start with history.  There is an active debate over whether, in the Eighteenth and Nineteenth  Centuries, the main function of punitive damages was to provide \u201cstealth\u201d  compensation for pain and suffering, since non-economic damages were allegedly  not available in tort during that period.  This view, which one might call the \u201ccrypto-compensation\u201d position, was  first embraced by the Court in <strong><i><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/532\/424.html\" rel=\"noopener\">Cooper  Industries, Inc. v. Leatherman Tool Group, Inc.<\/a><\/i><\/strong> in 2001, and it  is simply wrong. I have written a law  review article about this error in \u201cWhat Did Punitive Damages Do? Why Misunderstanding the History of Punitive  Damages Matters Today,\u201d 78 Chi-Kent L. Rev. 163 (2003), and I simply refer the  reader to it.<\/p>\n<p>Souter seems to back away from the Court\u2019s error in <i>Cooper Industries<\/i> by saying that it  really doesn\u2019t matter who is right in this debate, since all that matters is  that, today, there is a consensus that the purpose of punitive damages is to  punish. But that statement proves  exactly why the crypto-compensatory argument is dangerous.<\/p>\n<p>Souter assumes that since the purpose of punitive damages is  at least a \u201cnew\u201d form of punishment, its present purpose is neither informed  nor constrained by the past. Souter  assumes that the current purpose of punitive damages is to extend the state\u2019s  power to punish from the criminal realm into the realm of private law \u2013 that  is, civil cases such as this one. At one  point, he notes that variability in punitive damages might be permitted if they  allowed courts to reach \u201ca generally accepted optimal level of penalty and  deterrence.\u201d At another point, he  explicitly uses the evolution of the federal sentencing guidelines to justify  his conclusion that the best way to be fair to all defendants facing punitive  damages is to employ simple arithmetical ratios that do not depend on the  vagaries of human judgment.<\/p>\n<p>If one viewed the historical purpose of punitive damages as  permitted a special form of compensation\u2014that is, permitting compensation for  dignitary harms, by allowing victims of private wrongs to punish those who  violated their rights\u2014then there would be no need to identify some great break  in the history of punitive damages between the Nineteenth and Twentieth  Centuries. And the search for  mathematical equality\u2014which seems to drive Souter\u2019s opinion &#8212; would not be  placed at the center of the common law concept of punitive damages.<\/p>\n<p>Souter\u2019s mathematical argument is internally inconsistent as  well. He begins by admitting that there  is no evidence that, in the aggregate, punitive damages are awarded often, or  in very high ratios relative to the compensatory awards that they accompany. The problem, Souter says, is the <u>unpredictability<\/u> of the very rare and very high blockbuster award. But it is not clear why, in fact, that is a  problem from the point of view of deterrence, since the <i>ex ante<\/i> risk of a high-ratio award to any defendant is still quite  small. <\/p>\n<p>I can see why Souter might think that, from a fairness point  of view, this is a problem (imagine if out of every 10,000 speeding tickets,  one person is given a $1 million penalty), but the odd thing is that the <i>Exxon<\/i> case itself did not involve a  \u201cvery rare and very high\u201d award. The  punitive damages awarded by the jury were within the \u201csingle digit ratio\u201d (that  is, a ratio of punitive to compensatory damages with a single-digit numerator)  recommended by the Court in <strong><i><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/538\/408.html\" rel=\"noopener\">State  Farm Mut. Automobile Co. v. Campbell<\/a><\/i><\/strong>, and the award approved by  the Ninth Circuit was half that\u2014that is, it was five times the estimated  compensatory award, when even nine times would have fallen within the Court\u2019s  recommended ratio.<\/p>\n<p>There may be good reasons for concluding that, as a matter  of common law reasoning, the $5 billion punitive damages award should be  reversed. The problem is that the  reasons offered by the Court for objecting to the Ninth Circuit\u2019s review of \u2013  and reduction of &#8212; the trial jury\u2019s award are <i>ad hoc<\/i>, as is the Court\u2019s solution\u2014to impose a 1:1 ratio.<\/p>\n<p><strong>The Interesting Voting Blocs This Case  Created<\/strong><\/p>\n<p>Two important features of the five-member majority in this  case are worth noting. Moreover, the weakness of the majority opinion may  explain one feature about the voting pattern that produced it.<\/p>\n<p>First, Justices Scalia and Thomas voted to reverse the  award. This is important because it is  the first time that these justices have voted with a majority to reverse a  punitive damages award. Scalia,  especially, has, in the past, been scathing in his criticism of the Court\u2019s  decision to enter into the thicket of evaluating punitive damages awarded by  state juries.<\/p>\n<p>Of course, this case is different from all the previous  cases. <i>Exxon<\/i> did not involve the Constitution or the Due Process  Clause. One might think that Scalia saw  no reason to invoke the passive virtues (that is, the virtues of judicial  restraint and especially Supreme Court restraint) in a case involving federal  common law. However, this argument is  too clever by half, I think. Frankly, I  can\u2019t tell the difference between the common law virtues of fairness that led  Souter to impose a 1:1 ratio in this case, and the due process requirement of  fairness that led the Court to impose a \u201csingle-digit\u201d ratio in <i>State Farm<\/i> (which drives Scalia  bonkers).<\/p>\n<p>Second, the traditional coalition of moderates that has  supported the Court\u2019s evolving punitive damages jurisprudence since 1994, when  it reversed its first punitive damages award in <strong><i><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/517\/559.html\" rel=\"noopener\">BMW  of North America, Inc. v. Gore<\/a><\/i><\/strong>, broke apart in <i>Exxon<\/i>. <i>BMW\u2019s<\/i> majority, led by Justice  Stevens, included Justices Kennedy, Souter and Breyer. These four were part of the majority in <i>State Farm.<\/i> But now look at the majority in <i>Exxon<\/i>:  Souter, Roberts, Kennedy, Scalia and Thomas. Stevens and Breyer joined the dissent. <\/p>\n<p>To put it another way:  It has to be a little embarrassing for Souter and Kennedy to now be  forced to rely on Scalia and Thomas to cobble together a majority to reverse a  punitive damages award. The last fifteen  years of case law in this area suggests that the majority in <i>Exxon<\/i> may agree on only one thing: $5 billion, for whatever reason, is simply  too much money to demand of any tortfeasor.  On this point, at least, a majority of the Court agreed.<\/p>\n<hr size=\"1\">\n<p class=\"authorfoot\">\n\n<!-- BEGIN AUTHORS FOOTNOTE -->\n<a name=\"bio\"><\/a>\nAnthony J. Sebok, a FindLaw columnist, is a Professor at Benjamin N. Cardozo School of Law in New York City. His other columns on tort issues may be found in the archive of his columns on this site. \n<br><br>\n\n<\/p>\n\n\n\n\n    <\/div><div class=\"was-this-helpful\">\n    <div\n            class=\"was-this-helpful__question-container\"\n            aria-labelledby=\"was-this-helpful__question\"\n            role=\"group\"\n    >\n        <span\n                id=\"was-this-helpful__question\"\n                class=\"was-this-helpful__question fl-text-lg-bold\"\n        >Was this helpful?<\/span>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"Yes\"\n                value=\"yes\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">Yes<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-up\" clip-path=\"url(#clip0_604_3418)\">\n                        <path id=\"Vector\"\n                              d=\"M6 21H3C2.46957 21 1.96086 20.7893 1.58579 20.4142C1.21071 20.0391 1 19.5304 1 19V12C1 11.4696 1.21071 10.9609 1.58579 10.5858C1.96086 10.2107 2.46957 10 3 10H6M13 8V4C13 3.20435 12.6839 2.44129 12.1213 1.87868C11.5587 1.31607 10.7956 1 10 1L6 10V21H17.28C17.7623 21.0055 18.2304 20.8364 18.5979 20.524C18.9654 20.2116 19.2077 19.7769 19.28 19.3L20.66 10.3C20.7035 10.0134 20.6842 9.72068 20.6033 9.44225C20.5225 9.16382 20.3821 8.90629 20.1919 8.68751C20.0016 8.46873 19.7661 8.29393 19.5016 8.17522C19.2371 8.0565 18.9499 7.99672 18.66 8H13Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\"\n                              stroke-linejoin=\"round\"><\/path>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3418\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"><\/rect>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"No\"\n                value=\"no\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">No<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-down\" clip-path=\"url(#clip0_604_3423)\">\n                        <path id=\"Vector\"\n                              d=\"M16 0.999995H18.67C19.236 0.989986 19.7859 1.18813 20.2154 1.55681C20.645 1.9255 20.9242 2.43905 21 3V10C20.9242 10.5609 20.645 11.0745 20.2154 11.4432C19.7859 11.8119 19.236 12.01 18.67 12H16M9.00003 14V18C9.00003 18.7956 9.3161 19.5587 9.87871 20.1213C10.4413 20.6839 11.2044 21 12 21L16 12V0.999995H4.72003C4.2377 0.994543 3.76965 1.16359 3.40212 1.47599C3.0346 1.78839 2.79235 2.22309 2.72003 2.7L1.34003 11.7C1.29652 11.9866 1.31586 12.2793 1.39669 12.5577C1.47753 12.8362 1.61793 13.0937 1.80817 13.3125C1.99842 13.5313 2.23395 13.7061 2.49846 13.8248C2.76297 13.9435 3.05012 14.0033 3.34003 14H9.00003Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3423\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"\/>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n    <\/div>\n    <span class=\"was-this-helpful__taken-action fl-text-sm-bold\"><\/span>\n    <div class=\"was-this-helpful__feedback-container\">\n        <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n            <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n        <\/div>\n        <form class=\"was-this-helpful__feedback-form\">\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--positive\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this helpful?<\/legend>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--understandable\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Easy to understand\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--understandable\"\n                        >Easy to understand<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--solved-problem\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Solved my problem\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--solved-problem\"\n                        >Solved my problem<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--negative\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this not helpful?<\/legend>\n                    <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n                        <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--missing-info\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Missing Information\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--missing-info\"\n                        >Missing the information I need<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--complicated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Too complicated\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--complicated\"\n                        >Too complicated \/ too many steps<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--dated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Out of date\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--dated\"\n                        >Out of date<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--negative-other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--negative-other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__form-buttons-container\">\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--positive at-feedback-submit fl-button secondary\"\n                    type=\"submit\"\n                >\n                    <span class=\"fl-button-content\">Submit<\/span>\n                    <i\n                        class=\"fa fa-angle-right medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--cancel fl-button primary disabled\"\n                    type=\"reset\"\n                >\n                    <span class=\"fl-button-content\">Cancel<\/span>\n                    <i\n                        class=\"fa fa-times-circle medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n            <\/div>\n        <\/form>\n    <\/div>\n    <div class=\"was-this-helpful__thank-you-message\" role=\"status\">\n        <i class=\"was-this-helpful__thank-you-message-icon fa fa-check\"><\/i>\n        <p class=\"was-this-helpful__thank-you-message-text\" aria-live=\"polite\"><\/p>\n    <\/div>\n<\/div>\n\n\n    <\/div>\n    \n    <div class=\"fl-block-column fl-section-sidebar\">\n        \n    <\/div>\n<\/div>","protected":false},"parent":49876,"menu_order":0,"template":"app\/Http\/Controllers\/Templates\/ArticlePageController.php","meta":{"_acf_changed":false,"_stopmodifiedupdate":false,"_modified_date":"","_cloudinary_featured_overwrite":false},"class_list":["post-53634","supreme","type-supreme","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/53634","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme"}],"about":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/types\/supreme"}],"up":[{"embeddable":true,"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/49876"}],"wp:attachment":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/media?parent=53634"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}